Systems and methods for objective-based scoring using machine learning techniques

ABSTRACT

Certain aspects and features of the present disclosure relate to systems and methods that generate machine-learning models to predict whether user devices are likely to meet defined objectives. For example, a machine-learning model can be generated to predict whether or not a user device is likely to access a resource. In some implementations, a semi-supervised model can be used to determine to what extent user devices are predicted to satisfy the defined objective(s). For example, a resource-affinity parameter can be generated as a result of inputting various data points into a semi-supervised model. The various data points can be access from a plurality of data sources, and can represent one or more activities or attributes associated with a user. The value of the resource-affinity parameter can be evaluated to determine the extent to which the user is likely to meet an objective.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/983,475, filed on May 18, 2018, entitled “SYSTEMS ANDMETHODS FOR OBJECTIVE-BASED SCORING USING MACHINE LEARNING TECHNIQUES,”which claims the priority benefit of U.S. Provisional Patent ApplicationNo. 62/508,917, filed on May 19, 2017, entitled “SYSTEMS AND METHODS FOROBJECTIVE-BASED PREDICTION USING MACHINE LEARNING TECHNIQUES,” thedisclosures of which are hereby incorporated by reference in theirentirety for all purposes.

TECHNICAL FIELD

The present disclosure generally relates to dynamically assigning accessrights to resources in a hierarchical manner using machine-learningtechniques. More specifically, the present disclosure relates to systemsand methods for generating machine-learning models to predict useraffinities to resources.

BACKGROUND

Load management systems can process the assignment of access rights touser devices. For example, an access right can be configured to grant auser device access to a resource. Generally, assigning access rights touser devices occurs on a first-come-first-served basis. However,unauthorized activity, such as by hackers or bot scripts, has increased.For instance, bot scripts can be configured to mimic user devices toobtain access to resources in an unauthorized manner. As the load ofuser requests increases in scale (e.g., to big-data levels), securingload management systems against unauthorized activity becomes morechallenging. Automatically detecting unauthorized activity at a largescale and controlling workflows to manage or block the unauthorizedactivity has been inefficient and burdensome on network resources.

SUMMARY

The term embodiment and like terms are intended to refer broadly to allof the subject matter of this disclosure and the claims below.Statements containing these terms should be understood not to limit thesubject matter described herein or to limit the meaning or scope of theclaims below. Embodiments of the present disclosure covered herein aredefined by the claims below, not this summary. This summary is ahigh-level overview of various aspects of the disclosure and introducessome of the concepts that are further described in the DetailedDescription section below. This summary is not intended to identify keyor essential features of the claimed subject matter, nor is it intendedto be used in isolation to determine the scope of the claimed subjectmatter. The subject matter should be understood by reference toappropriate portions of the entire specification of this disclosure, anyor all drawings and each claim.

Embodiments of the present disclosure include a computer-implementedmethod. The method may include receiving, at a primary load managementsystem, a communication from a user device, the communicationcorresponding to a request for one or more access rights to a resource.The primary load management system may manage assignment of accessrights to resources. The method may also include determining a useridentifier associated with the user device. The determination of theuser identifier may be based on the communication. The method mayinclude accessing one or more data points associated with the useridentifier. Each data point of the one or more data points maycorrespond to an attribute associated with the user identifier. Themethod may include generating a resource-affinity parameter using theone or more data points. The resource-affinity parameter may represent alikelihood that a user associated with the user device will meet anobjective. The resource-affinity parameter may be generated by inputtingthe one or more data points into a machine-learning model to output theresource-affinity parameter. The method may include determining acurrent system load, wherein the current system load represents a loadof requests received at the primary load management system during acurrent time period. The method may include determining a first throttlefactor based on the resource-affinity parameter and the current systemload. The first throttle factor may control a first workflow associatedwith a resource. The method may include enabling the user device toquery a plurality of access rights associated with the resource. Theuser device may be enabled to query the plurality of access rights aspart of the first workflow controlled by the first throttle factor, andthe query may include a constraint for querying the plurality of accessrights.

The method may further include receiving a request for one or moreaccess rights of the plurality of access rights associated with theresource; and determining a second throttle factor based on theresource-affinity parameter. The second throttle factor may control asecond workflow associated with assigning the one or more access rightsto the user device.

Certain embodiments may also include a system. The system may includeone or more data processors; and a non-transitory computer-readablestorage medium containing instructions which, when executed on the oneor more data processors, cause the one or more data processors toperform operations including the method(s) described above and herein.

Certain embodiments may also include a computer-program product tangiblyembodied in a non-transitory machine-readable storage medium, includinginstructions configured to cause a data processing apparatus to performoperations including the method(s) described above and herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The specification makes reference to the following appended figures, inwhich use of like reference numerals in different figures is intended toillustrate like or analogous components.

FIG. 1 depicts a block diagram of an embodiment of a resourceaccess-facilitating interaction system;

FIG. 2 shows an illustration of hardware and network connections of aresource access-facilitating interaction system according to anembodiment of the invention;

FIG. 3 shows an illustration of a communication exchange betweencomponents involved in a resource access-facilitating interaction systemaccording to an embodiment of the invention;

FIG. 4 illustrates example components of a device;

FIG. 5 illustrates example components of resource access coordinatormodule;

FIG. 6 illustrates a flowchart of an embodiment of a process forassigning access rights for resources;

FIGS. 7A and 7B show embodiments of site systems in relations to mobiledevices;

FIG. 8 shows a block diagram of user device according to an embodiment;

FIG. 9 illustrates sample components of an embodiment of site system180, including connections to a NAS and access management system;

FIGS. 10A and 10B illustrate examples of communication exchangesinvolving primary and secondary load management systems.

FIG. 11 is a block diagram illustrating a network environment forenabling access rights to be queried in a hierarchical manner based onresource-affinity parameters.

FIG. 12 is a swimlane diagram illustrating an example data flow of thenetwork environment of FIG. 11.

FIG. 13 is a block diagram illustrating a network environment forgenerating contextualized resource-affinity parameters using global andlocal resource-affinity parameters.

FIG. 14 is a block diagram illustrating a network environment forthrottling access rights assignment workflows based on current systemload.

FIG. 15 is a flow diagram illustrating an embodiment of a process forcontinuously modifying queues during the different time periods.

DETAILED DESCRIPTION

Certain aspects and features of the present disclosure relate to systemsand methods that generate machine-learning models to predict whetheruser devices will meet defined objectives. In some implementations, if auser device is predicted to meet an objective, a load management systemcan grant the user device access to resources, whereas, if a user deviceis predicted to not meet the objective, the load management system candeny access to the resources. An objective can be defined at a primaryload management system that generates and manages the assignment ofaccess rights to resources. Non-limiting examples of objectives mayinclude accessing a resource during a defined time period, requestingadditional items associated with a resource during the defined timeperiod, reassigning access rights to secondary load management systems,reassigning access rights to another user device, association withadditional user devices, and other suitable objectives.

In some implementations, the primary load management system can generatea machine-learning model, which can process one or more data points tooutput a result that can be used to predict a likelihood that a userdevice will meet an objective in the future. For example, amachine-learning model can evaluate user data (e.g., one or more datapoints) associated with a user device that is requesting assignment ofan access right to a resource. The result (generated after processingthe one or more data points using the machine-learning model) can beused to determine whether or not the user device is likely to access theresource during a defined time period. In some cases, a user device maybe assigned an access right, but may ultimately not access the resourceduring the defined time period. Instead, the user device may transferthe access right to another user device or to a secondary loadmanagement system. If accessing the resource during the defined timeperiod is the defined objective, then a user device does not meet thatobjective if the user device transfers the access right to another userdevice, for example. The one or more data points can include dataassociated with the user device. Further, the one or more data pointsmay be factors or attributes associated with meeting the objective ornot meeting the objective.

In some implementations, a semi-supervised model can be used todetermine to what extent user devices (e.g., users associated with userdevices or user profiles) are predicted to satisfy the definedobjective(s). For example, user data (described in greater detailherein) associated with a particular user may be evaluated using amachine-learning model. The result of evaluating the user data using themachine-learning model may be a resource-affinity parameter. As anon-limiting example, user data may include various data points, whichare inputted into a semi-supervised machine-learning model. The outputof the semi-supervised machine-learning model may be a resource-affinityparameter (e.g., an integer or non-integer score or value, an array ormatrix of values, a letter score, a numerical score, a score representedby a symbol, etc.). The resource-affinity parameter may represent aprediction of whether or not the user or user device associated with theinputted user data will meet the objective. In some cases, theresource-affinity itself may represent the prediction as to whether ornot the user device will meet the objective. In some cases, theprediction may be determined by comparing the resource-affinityparameter to one or more threshold values or one or more threshold valueranges to determine whether the user is likely to meet the objective. Itwill be appreciated that unsupervised, supervised, ensemble techniques,and/or batch-learning models can be used instead of or in additional tosemi-supervised models.

According to certain implementations, the primary load management systemcan assign access rights associated with a resource to user devices forwhich the resource-affinity parameter indicates a prediction to meet anobjective (e.g., the user device will likely access the resource duringa defined time period). Advantageously, the primary load managementsystem can use the resource-affinity parameter to assign access rightsto the user devices that will likely access the associated resourceduring the time period, and thus, avoid or reduce the chances ofassigning access rights to user devices that may not ultimately accessthe resource during the time period. In some implementations, theprimary load management system can identify that a particular accessright with a particular characteristic or attribute is available to beassigned to user devices. Before allowing the particular access right tobe queried by user devices for the purpose of requesting assignment, theprimary load management system can determine one or more user devicesthat are predicted to meet the objective (e.g., based on the respectiveresource-affinity parameter), and automatically and/or tentativelyassign the particular access right for those one or more user devices.In some implementations, the resource-affinity parameter can begenerated for each user device (e.g., a user registered with the primaryload management system) to determine a degree or extent to which theuser device is predicted to meet the objective. Automatically and/ortentatively assigning the access right for a particular user deviceprevents that access right from being queriable by other user devicesquerying databases for the purpose of requesting assignment of accessrights. In some cases, a workflow can be executed to automaticallyassign the access right to the particular user device. In some cases,the workflow can be executed to cause a communication (e.g., a textmessage using a Short Message Service (SMS) or a push notification usinga native application) to be transmitted to the particular user device.The communication may include a link that, when selected, facilitatesthe completion of an assignment process for assigning the access rightto the user device.

Advantageously, the embodiments described herein may provide a technicalsolution to the technical problem of overloaded servers and/or queuesduring time periods when access rights are available to user devices forassignment. Instead of processing requests for access rights (receivedfrom user devices) sequentially or in batches from a queue (which maycause servers to be overloaded when requests are received from userdevices at a large scale, such as at big-data levels), the primary loadmanagement system can automatically and/or tentatively assign the accessrights for user devices based on the resource-affinity parameter, whichis calculated using machine-learning models before the time period whenthe access rights are available to user devices for assignment.Automatically and/or tentatively assigning the access rights for userdevices based on the resource-affinity parameters can improve the usageof processing resources in networked systems because the user devices nolonger need to request an assignment. Rather, access rights can beautomatically and/or tentatively assigned for user devices without theuser devices requesting assignment for the access rights, which reducesthe number of communications received at the primary load managementsystem. Thus, networked servers avoid being overloaded with requests,and access rights are assigned to user devices that will likelyultimately access the resource during defined time periods, rather thanto user devices that are likely to transfer the access right to otheruser devices.

In some implementations, the primary load management system can computea resource-affinity parameter for each user or user device registeredwith the primary load management system. The primary load managementsystem can identify the highest resource-affinity parameter (or thegroup of resource-affinity parameters that are within a range), anddetermine the user associated with that resource-affinity parameter.Further, the primary load management system may transmit a communication(using a messaging system or service, such as an SMS provider, or a pushnotification using a native application) to a mobile device operated bythe user associated with the highest resource-affinity parameter. Thecommunication can include a notification that one or more access rightshave been Automatically and/or tentatively assigned for the user for atemporary period of time (e.g., 15 minutes). If the user transmits aparticular message back to the primary load management system (e.g., atext message including the word “YES”) using the mobile device, the oneor more access rights (e.g., electronic tickets) to a resource (e.g., anevent) can be automatically assigned to the user. In theseimplementations, the access rights that are automatically and/ortentatively assigned to the users are not publically queriable oravailable for querying by other user devices that access an interfaceassociated with the primary load management system. Further, if the userdecides not to proceed with completing the assignment of the accessright (e.g., the user does not text back “YES” within a defined timeperiod), the primary load management system can iteratively identifyanother user with the next highest resource-affinity parameter andtransmit the notification to a mobile device operated by that otheruser, and so on. Advantageously, iteratively assigning access rights touser devices can reduce the system load experienced at the primary loadmanagement system when access rights are available to be assigned touser devices, thereby providing an efficient process for load balancingprocessing resources within the network.

In some examples, the primary load management system may notautomatically and/or tentatively assign an access right for the userwith the highest resource-affinity parameter. In these examples, when anaccess right becomes available for assignment (e.g., available forpurchasing by a user), the primary load management system may transmit anotification to one or more user devices. The one or more user devicesmay be operated by users associated with resource-affinity parametersabove a certain threshold, for example, indicating that the users arelikely to meet an objective. The notification may include a message thatindicates the access right is available for assignment. In someimplementations, the message may include a link to an interface thatenables a user to enter a process to have that access right assigned tothe user. For example, the link may be to a website associated with theprimary load management system. In these examples, the user may benotified of the newly-available access rights and provided with anopportunity to complete an assignment process that assigns the accessrights to the user before the availability of the newly-available accessrights is publicly known. In some cases, the newly-available accessrights may or may not be publically available for querying by other userdevices accessing the primary load management system.

In some implementations, the resource-affinity parameter that isgenerated for each user (e.g., a user who is registered or who has notregistered yet with the primary load management system) may indicate adegree to which the user is predicted to meet the objective. Theresource-affinity parameter can be contextual to a specific resource(e.g., an event). For example, the resource-affinity parameter can begenerated as a combination of a global parameter (e.g., aresource-affinity parameter representing the likelihood a user willaccess a resource generally) and a local parameter (e.g., aresource-affinity parameter representing the likelihood a user willaccess a specific resource, such as a particular event). Thecontextualization of resource-affinity parameters is described infurther detail with respect to FIG. 13.

In addition, generating a resource-affinity parameter can includeinputting one or more data points into a machine-learning model (e.g., asupport vector machine (SVM)). Data points (e.g., user data) can includeinformation about a user or user device and may be stored across one ormore data stores. Non-limiting examples of data points can include aphone number, an email address, previous resource-access history (e.g.,how many resources were previously accessed by this user or userdevice), previous assignment history (e.g., how many access rights werepreviously assigned to this user or user device), previous transferhistory (e.g., how many times has this user or user device transferredan access right to another user or to a secondary load managementsystem), affinities posted by the user on social media systems (e.g.,“liked,” “shared,” or “favorited” the resource on a social mediawebsite), video or audio data streams associated with the user or userdevice (e.g., on a music platform), or any other suitable data pointthat can be used to predict a likelihood of meeting an objective. Thedata points associated with the user can be passed through themachine-learning model (e.g., a semi-supervised model) to generate aresource-affinity parameter for that user. The generatedresource-affinity parameter can represent an affinity towards accessingresources generally or a specific resource. Further, the generatedresource-affinity parameter can be evaluated to predict whether the useris likely to satisfy the objective or not. In some implementations, themachine-learning model can be generated using unsupervised,semi-supervised, or supervised machine-learning techniques. For example,the machine-learning model can be defined by labeling data points from atraining data set (e.g., data points associated with or representing apopulation of users). To illustrate and as a non-limiting example, ifthe objective is defined as accessing a particular resource during adefined time period (e.g., the event time), the machine-learning modelcan include data points that are labeled to indicate a likelihood ofaccessing a resource (or alternatively, a likelihood of not accessing aresource, such as a likelihood of transferring the access right toanother user device). The data points associated with the user can bepassed through the machine-learning model and compared against thelabeled data points to output a resource-affinity parameter (e.g., avalue or score that can be used or compared against a threshold topredict whether the user will satisfy the objective).

In some implementations, when a user device initiates a process flow orworkflow (e.g., a process flow for requesting assignment of an accessright), the resource-affinity parameter associated with that user devicecan be evaluated to modify the process flow based on the value of theresource-affinity parameter. For example, when the user device initiatesa process flow for requesting assignment of an access right, the processflow may be improved, optimized, or enhanced (e.g., by modifyingprocessing delays to improve the speed of completing the process flow)when the user device is associated with a resource-affinity parameterthat meets or exceeds a threshold, is within a threshold range, or thatindicates a likelihood of meeting an objective. Conversely, when theuser device initiates a process flow for requesting assignment of anaccess right, the process flow may be delayed or made slower (or certainsteps of the flow may be removed) when the user device is associatedwith a resource-affinity parameter that does not meet or exceed athreshold, is outside a threshold range, or that indicates a likelihoodof not meeting an objective.

In some implementations, modifying the process flow can includemodifying a position of an assignment request in a queue based on theresource-affinity parameter associated with the user device. Forexample, during a time period when one or more access rights areavailable for assignment, and thus, available to be queried by userdevices, the primary load management system may generate a digital queueof user requests for access-right assignment. For example, if a userdevice (that has not been queued yet) requests assignment of an accessright to a resource, the primary load management system may retrieve orgenerate a resource-affinity parameter for the user to identify where toposition the request in an existing queue of requests. If theresource-affinity parameter (e.g., as compared to a threshold) indicatesthat the user device is likely to access the resource (e.g., attend theevent), then the user device may be positioned in an advantageous orbeneficial position in the queue (e.g., at a queue position that will beprocessed earlier than others) so that the user can request assignmentfor more favorable access rights than other user devices (that may beassociated with lower resource-affinity parameters).

These illustrative examples are given to introduce the reader to thegeneral subject matter discussed here and are not intended to limit thescope of the disclosed concepts. The following sections describe variousadditional features and examples with reference to the drawings in whichlike numerals indicate like elements, and directional descriptions areused to describe the illustrative embodiments but, like the illustrativeembodiments, should not be used to limit the present disclosure. Theelements included in the illustrations herein may not be drawn to scale.

FIG. 1 depicts a block diagram of an embodiment of a resource managementsystem 100, according to an embodiment of the present disclosure. Mobiledevice 110 (which can be operated by a user 105) and an event-providerdevice 120 (which can be operated, controlled, or used by an eventprovider 115) can communicate with an access management system 185directly or via another system (e.g., via an intermediate system 150).Mobile device 110 may transmit data to access point 145, which isconnected to network 155, over communication channel 140 using antennae135. While FIG. 1 illustrates mobile device 110 communicating withaccess point 145 using a wireless connection (e.g., communicationchannel 140), in some embodiments, mobile device 110 may alsocommunicate with access point 145 using a wired connection (e.g., anEthernet connection). Mobile device 110 can also communicate with one ormore client devices, such as a client agent device 170 operated by aclient agent 175, a client register 160 or a client point device 165using a wired or wireless connection. In addition, using the accessmanagement system 185, an event provider 115 can identify an event, aparameter of attending the event, a date or dates of the event, alocation or locations of the event, etc. Each inter-system communicationcan occur over one or more networks 155 and can facilitate transmissionof a variety of types of data. It will be understood that, although onlyone of various systems, devices, entities and network are shown, theresource management system 100 can be extended to include multiple ofany given system(s), device(s), entity(ies), and/or networks.

Access management system 185 can be configured to manage a dynamic setof access rights to one or more resources. More specifically, accessmanagement system 185 can track which resources are to be made availableto users, specifications of the resources and times at which they willbe available. Access management system 185 can also allocate accessrights for resources and facilitate transmissions of notifications ofthe available rights to a set of user devices. For example, accessmanagement system 185 can alert users of the availability via a website,app page or email. As another example, access management system cantransmit data about access rights and resources to one or moreintermediate systems 150, which can facilitate distribution ofaccess-right availability and processing of requests for such rights.

Notifications of available access rights can be accompanied by optionsto request that one or more access rights be assigned to a user.Therefore, user 105 can provide input to mobile device 110 via aninterface to request such assignment and provide other pertinentinformation. Intermediate system 150 and/or access management system 185can process the request to ensure that the requested access right(s)remain available and that all required information has been receivedand, in some instances, verified. Thereafter, access management system185 can assign one or more access rights to the user, e.g., matching theaccess rights requested by the user.

Assigning an access right can include, for example, associating anidentifier of the right with an identifier of a user, changing a statusof the right from available to assigned, facilitating a cease innotifications that the access right is available, generating anaccess-enabling code to use such that the corresponding access will bepermitted and/or generating a notification to be received at mobiledevice 110 confirming the assignment and/or including data required forcorresponding access to be permitted.

In some instances, a resource is at least partly controlled, by aclient. The resource may be accessed at a particular location orstructure, and a variety of client devices may be present at thelocation so as to facilitate usage of an access right. Exemplary clientdevices can include client agent device 170, which can be one operatedby a client agent 175 (e.g., a human client agent), a client register160 (e.g., which can operate independently of an agent and/or can beconnected to or include a device that, while in a locked mode, canimpede resource access, such as a turnstile) and client point device 165(e.g., which can operate independently of an agent and/or can bepositioned at or around the resource-associated location. For example,in some instances client agent device 170 can be operated by an agent ata location for a resource that is an event (“event resource”) takingplace at the location. In this example, client agent device 170 is usedby an agent that is manning an entrance to the location (e.g., which caninclude, for example, a location of a structure or a geographic region)or a part thereof; client register 160 can be or can be connected to aturnstile, gate or lockable door that is positioned along a perimeter orentrance to a resource-associated location or part thereof; and clientpoint device 165 can be an electronic device positioned at or within aresource-associated location.

In some instances, mobile device 110 performs particular functions upondetecting a client device and/or the contrary. For example, mobiledevice 110 may locally retrieve or request (e.g., from an externalsource) an access-enabling code. The access-enabling code can betransmitted to the client device or a remote server (e.g., a serverhosting access management system 185) for evaluation and/or can belocally evaluated. The evaluation can include, for example, confirmingthat the access-enabling code has a particular characteristic or format(e.g., generally or one characteristic corresponding to a particularresource or type of access), matches one in an access-enabling code datastore and/or has not been previously redeemed. A result of theevaluation can be locally displayed at an evaluating device, can controla device component (e.g., a physical access control module), and/or canbe transmitted to another device, such as mobile device 110.

In some instances, user 105 can use multiple mobile devices 110 toperform various operations (e.g., using one device to request an accessright and another to interact with client devices). Some instances ofmobile device 110, access management system 185, intermediate system150, client agent device 170, client register 160 and/or client pointdevice 165 can include a portable electronic device (e.g., a smartphone, tablet, laptop computer or smart wearable device) or anon-portable electronic device (e.g., one or more desktop computers,servers and/or processors).

In exemplary embodiments, access rights can be represented in datamaintained at a client device or at access management system 185. Forexample, a database or data store include a list of identifiers for eachuser or user device having an assigned access right for a resource orassociating an identifier for each user or user device with anidentifier of a particular access right. In some instances, indicia canbe transmitted to a user device that indicates that an access right isavailed. In various instances, it may be permitted or prohibited for theindicia to be transferred. The indicia may be provided as part of anelectronic or physical object (e.g., a right to access an event) orindependently. The indicia may include an access-enabling code.

In some instances, access management system 185 communicates with one ormore intermediate systems 150, each of which may be controlled by adifferent entity as compared to an entity controlling access managementsystem 185. For example, access management system 185 may assign accessrights to intermediate systems 150 (e.g., upon acceptance of terms).Intermediate system 150 can then collect data pertaining to the assignedaccess rights and/or a corresponding event, can format and/or edit thedata, generate a notification of availability of the access rights thatincludes the formatted and/or edited data and facilitate presentation ofthe notification at a mobile device 110. When intermediate system 150receives a communication from the mobile device 110 indicative of anaccess-right request, intermediate system 150 can facilitate assignment(or reassignment) of an access right to the user (e.g., by transmittingrelevant information to access management system 185 identifying theuser and/or user device and/or by transmitting relevant information tomobile device 110 pertaining to the access right).

A resource can include one managed or provided by a client, such as anentity or an entity operating a spatial region. A mobile device 110 cantransmit data corresponding to the access right (e.g., anaccess-enabling code) to a client device upon, for example, detectingthe client device, detecting that a location of the mobile device 110 iswithin a prescribed geographical region, or detecting particular input.The receiving client device may include, for example, a client agentdevice 170 operated at an entrance of a defined geographical location ora client register 160 that includes or is attached to a lockingturnstile. The client device can then analyze the code to confirm itsvalidity and applicability for a particular resource and/or access type,and admittance to the event can be accordingly permitted. For example, aturnstile may change from a locked to an unlocked mode upon confirmationof the code's validity and applicability.

Each of the depicted devices and/or systems may include a software agentor application (“app”) that, when executed, performs one or more actionsas described herein. In some instances, a software agent or app on onedevice is, at least in part, complementary to a software agent or app onanother device (e.g., such that a software agent or app on mobile device110 is, at least in part, complementary to at least part of one onaccess management system 185 and/or a client device; and/or such that asoftware agent or app on intermediate system 150 is, at least in part,complementary to at least part of one on access management system 185).

In some instances, a network in the one or more networks 155 can includean open network, such as the Internet, personal area network, local areanetwork (LAN), campus area network (CAN), metropolitan area network(MAN), wide area network (WAN), wireless local area network (WLAN), aprivate network, such as an intranet, extranet, or other backbone. Insome instances, a network in the one or more networks 155 includes ashort-range communication channel, such as Bluetooth or Bluetooth LowEnergy channel. Communicating using a short-range communication such asBLE channel can provide advantages such as consuming less power, beingable to communicate across moderate distances, being able to detectlevels of proximity, achieving high-level security based on encryptionand short ranges, and not requiring pairing for inter-devicecommunications.

In one embodiment, communications between two or more systems and/ordevices can be achieved by a secure communications protocol, such assecure sockets layer (SSL), transport layer security (TLS). In addition,data and/or transactional details may be encrypted based on anyconvenient, known, or to be developed manner, such as, but not limitedto, DES, Triple DES, RSA, Blowfish, Advanced Encryption Standard (AES),CAST-128, CAST-256, Decorrelated Fast Cipher (DFC), Tiny EncryptionAlgorithm (TEA), eXtended TEA (XTEA), Corrected Block TEA (XXTEA),and/or RC5, etc.

It will be appreciated that, while a variety of devices and systems areshown in FIG. 1, in some instances, resource management system 100 caninclude fewer devices and/or systems. Further, some systems and/ordevices can be combined. For example, a client agent device 170 may alsoserve as an access management system 185 or intermediate system 150 soas to as to facilitate assignment of access rights.

As described in further detail herein, an interaction between mobiledevice 110 and a client device (e.g., client agent device 170, clientregister 160 or client point device 165) can facilitate, for example,verification that user 105 has a valid and applicable access right,obtaining an assignment of an access right, and/or obtaining anassignment of an upgraded access right.

In addition, mobile device 110-2, which is operated by user 125-2, mayinclude a user device that is located at a spatial region of theresource (e.g., venue) during a time period for which the resource isaccessible (e.g., event time). Mobile device 110-2 may directly interactwith a client device (e.g., client agent device 170, client register 160or client point device 165), which is also located at the spatial regionduring the time period in which the resource is accessible using accessrights. As such, the access management system 185 may be updated oraccessed by mobile device 110-2 via the client agent device 170. Forexample, mobile device 110-2 may communicate with the client agentdevice 170 over a short-range communication channel 190, such asBluetooth or Bluetooth Low Energy channel, Near Field Communication(NFC), Wi-Fi, RFID, Zigbee, ANT, etc. Communicating using a short-rangecommunication such as BLE channel can provide advantages such asconsuming less power, being able to communicate across moderatedistances, being able to detect levels of proximity, achievinghigh-level security based on encryption and short ranges, and notrequiring pairing for inter-device communications. After the short-rangecommunication link 190 is established, mobile device 110-2 maycommunicate with the access management system 185 and access the item oritems of resources. That is, while mobile device B is configured tocommunicate over network 155, mobile device 110-2 may communicate withthe access management system 185 via the client agent device 170,instead of the network 155.

It will be appreciated that various parts of system 100 can begeographically separated. It will further be appreciated that system 100can include a different number of various components rather than anumber depicted in FIG. 1. For example, two or more of access assignmentsystems 185; one or more site systems 180; and intermediate system 150may be located in different geographic locations (e.g., differentcities, states or countries).

FIG. 2 shows an illustration of hardware and network connections of aresource access-facilitating interaction system 200 according to anembodiment of the invention. Each of various user devices 210-1, 210-2,210-3, 210-4 and 210-5 can connect, via one or more inter-networkconnection components (e.g., a router 212) and one or more networks 270to a primary assignment management system 214 or a secondary assignmentmanagement system 216-1, 216-2 or 216-3.

Primary assignment management system 214 can be configured to coordinateand/or control initial assignment of access rights. Secondary assignmentmanagement system 216 can be configured to coordinate and/or controlreassignment and/or transfer of access rights (e.g., from one user oruser device to another or from an intermediate agent to a user or userdevice). Secondary assignment management system 216 may also managetransfer offers (e.g., to allow a first user to identify a price atwhich a transfer request would be granted and to detect if a validrequest is received). It will be appreciated that, although primaryassignment management system 214 is shown to be separate from eachsecondary assignment management system 216, in some instances, anassignment management system may relate to both a primary and secondarychannel, and a single data store or a localized cluster of data storesmay include data from both channels.

Each of primary access assignment system 214 and secondary accessassignment system 216 can include a web server 218 that processes andresponds to HTTP requests. Web server 218 can retrieve and deliverweb-page data to a user device 210 that, for example, identify aresource, identify a characteristic of each of one or more access rightsfor the resource, include an invitation to request assignment of anaccess right, facilitate establishment or updating of a profile, and/oridentify characteristics of one or more assigned access rights. Webserver 218 can be configured to support server-side scripting and/orreceive data from user devices 210, such as data from forms or fileuploads.

In some instances, a web server 218 can be configured to communicatedata about a resource and an indication that access rights for theresource are available. Web server 218 can receive a requestcommunication from a user device 210 that corresponds to a request forinformation about access rights. The request can include one or moreconstraints, which can correspond to (for example) values (e.g., to bematched or to define a range) of particular fields.

A management server 222 can interact with web server 218 to provideindications as to which access rights' are available for assignment,characteristics of access rights and/or what data is needed to assign anaccess right. When requisite information is received (e.g., about a userand/or user device, identifying a final request for one or more accessrights, including payment information, and so on), management server 222can coordinate an assignment of the one or more access rights. Thecoordination can include updating an access-right data store to change astatus of the one or more access rights (e.g., to assigned); toassociate each of the one or more access rights with a user and/or userdevice; to generate or identify one or more access-enabling codes forthe one or more access rights; and/or to facilitate transmissionreflecting the assignment (e.g., and including the one or moreaccess-enabling codes) to a user device.

Management server 222 can query, update and manage an access-right datastore to identify access rights' availability and/or characteristicand/or to reflect a new assignment. The data store can include oneassociated with the particular assignment system. In some instances, thedata store includes incomplete data about access rights for a resource.For example, a data store 224 at and/or used by a secondary accessassignment system 216 may include data about an incomplete subset ofaccess rights that have been allocated for a particular resource. Toillustrate, a client agent may have indicated that an independentintermediary system can (exclusively or non-exclusively) coordinateassignment of a portion of access rights for a resource but not theremainder. A data store 224 may then, for example, selectively includeinformation (e.g., characteristics, statuses and/or assignmentassociations) for access rights in the portion.

Data store 224 or 226 associated with a particular primary or secondaryaccess assignment system can include assignment data for a set of accessrights that are configured to be set by the particular primary orsecondary access assignment system or by another system. For example, arule can indicate that a given access right is to have an availablestatus until a first of a plurality of access assignment systems assignsthe access right. Accordingly, access assignment systems would then needto communicate to alert each other of assignments.

In one instance, management server 222 (or another server in an accessassignment system) sends a communication to a central data managementserver farm 228 reflecting one or more recent assignments. Thecommunication may include an identification of one or more accessrights, an indication that the access right(s) have been assigned, anidentification of a user and/or user device associated with theassignment and/or one or more access-enabling codes generated oridentified to be associated with the assignment. The communication canbe sent, for example, upon assigning the access right(s), as a precursorto assigning the access right(s) (e.g., to confirm availability and/orrequest assignment authorization), at defined times or time intervalsand/or in response to an assignment-update request received from datamanagement server farm 228.

Data management server farm 228 can then update a central data store toreflect the data from the communication. The central data store can bepart of, for example, a network-attached storage 232 and/or astorage-area network 234.

In some instances, a data store 224 or 226 can include a cache, thatincludes data stored based on previous communications with datamanagement server farm 228. For example, data management server farm 228may periodically transmit statuses of a set of access rights (e.g.,those initially configured to be assignable by an access assignmentsystem) or an updated status (e.g., indicating an assignment) of one ormore access rights. As another example, data management server farm 228may transmit statuses upon receiving a request from an access assignmentsystem for statuses and/or authorization to assign one or more accessrights.

An access assignment system may receive statuses less frequently or attimes unaligned with requests received from user devices requestinginformation about access rights and/or assignments. Rather than initiatea central data store query responsive to each user-device request, amanagement server 222 can rely on cached data (e.g., locally cacheddata) to identify availability of one or more access rights, as reflectin webpage data and/or communications responsive to requestcommunications for access-right information. After requisite informationhas been obtained, management server 222 can then communicate with datamanagement server farm 228 to ensure that one or more particular accessrights have remained available for assignment.

In some instances, one or more of primary access assignment system 214and/or a secondary access assignment system 214 need not include a localor system-inclusive data store for tracking access-right statuses,assignments and/or characteristics. Instead, the access assignmentsystem may communicate with a remote and/or central data store (e.g.,network-attached storage 232 or storage-area network 234).

Access management system 120 can include a primary access assignmentsystem 214 and/or a secondary access assignment system 214; datamanagement server farm 228; and/or a central data store (e.g.,network-attached storage 232 or storage-area network 234). Each of oneor more intermediate systems 130 can include a primary access assignmentsystem 214 and/or a secondary access assignment system 214.

Data management server farm 228 may periodically and/or routinely assessa connection with an access assignment system 214. For example, a testcommunication can be sent that is indicative of a request to respond(e.g., with particular data or generally). If a response communicationis not received, if a response communication is not received within adefined time period and/or if a response communication includesparticular data (e.g., reflecting poor data integrity, network speed,processing speed, etc.), data management server farm 228 may reconfigureaccess rights and/or permissions and/or may transmit anothercommunication indicating that assignment rights of the access assignmentsystem are limited (e.g., to prevent the system from assigning accessrights).

It will be appreciated that various parts of system 200 can begeographically separated. For example, two or more of primary accessassignment system 214; one or more of secondary access assignmentsystems 214; and data management server farm 228 may be located indifferent geographic locations (e.g., different cities, states orcountries).

It will further be appreciated that system 200 can include a differentnumber of various components rather than a number depicted in FIG. 2.For example, system 200 can include multiple data management serverfarms 228, central data stores and/or primary access assignment systems214 (e.g., which can be geographically separated, such as being locatedin different cities, states or countries). In some instances, processingmay be split (e.g., according to a load-balancing technique) acrossmultiple data management server farms 228 and/or across multiple accessassignment systems 214. Meanwhile, the farms and/or systems can beconfigured to accept an increased or full load should another farmand/or system be unavailable (e.g., due to maintenance). Data stored ina central data store may also be replicated in geographically separateddata stores.

FIG. 3 shows an illustration of a communication exchange betweencomponents involved in a resource access-facilitating interaction system300 according to an embodiment of the invention. A user device 310 cansend one or more HTTP requests to a web-server system 318, andweb-server system 318 can respond with one or more HTTP responses thatinclude webpage data. The webpage data can include, for example,information about one or more resources, characteristics of a set ofaccess rights for each of the one or more resources, availability of oneor more access rights, an invitation to request an assignment of one ormore access rights and/or indications as to what information is requiredfor an access-right assignment. HTTP requests can includeassignment-request data (e.g., a resource identification, requisiteinformation, and/or an identification of an access-right constraint oraccess right).

Web-server system 318 can include one or more web processors (e.g.,included in one or more server farms, which may be geographicallyseparated) to, for example, map a path component of a URL to web data(e.g., stored in a local file system or generated by a program);retrieve the web data; and/or generate a response communicationincluding the web data. Web processor can further parse communication toidentify input-corresponding data in HTTP requests, such as field valuesrequired for an access-right assignment.

Web-server system 318 can also include a load balancer to distributeprocessing tasks across multiple web processors. For example, HTTPrequests can be distributed to different web processors. Load-balancingtechniques can be configured so as, for example, to distributeprocessing across servers or server farms, decrease a number of hopsbetween a web server and user device, decrease a geographical locationbetween a user device and web server, etc.

Web-server system 318 can further include a RAID component, such as aRAID controller or card. A RAID component can be configured, forexample, to stripe data across multiple drives, distribute parity acrossdrives and/or mirror data across multiple drives. The RAID component canbe configured to improve reliability and increase request-processingspeeds.

Web-server system 318 can include one or more distributed,non-distributed, virtual, non-virtual, local and/or remote data stores.The data stores can include web data, scripts and/or content object(e.g., to be presented as part or web data).

Some HTTP requests include requests for identifications of access-rightcharacteristics and/or availability. To provide web data reflecting suchinformation, web-server system 318 can request the information fromanother server, such as an SQL system 341 (e.g., which may include oneor more servers or one or more server farms).

SQL system 341 can include one or more SQL processors (e.g., included inone or more server farms, which may be geographically separated). SQLprocessors can be configured to query, update and otherwise use one ormore relational data stores. SQL processors can be configured to execute(and, in some instances, generate) code (e.g., SQL code) to query arelational data store.

SQL system 341 can include a database engine, that includes a relationalengine, OLE database and storage engine. A relational engine canprocess, parse, compile, and/or optimize a query and/or makequery-associated calls. The relational engine can identify an OLE DB rowset that identifies the row with columns matching search criteria and/ora ranking value. A storage engine can manage data access and use therowset (e.g., to access tables and indices) to retrieve query-responsivedata from one or more relational databases.

SQL system 341 can include one or more distributed, non-distributed,virtual, non-virtual, local and/or remote relational data stores. Therelational databases can include linked data structures identifying, forexample, resource information, access-right identifications andcharacteristics, access-right statuses and/or assignments, and/or userand/or user profile data. Thus, for example, use of the relationalstructures may facilitate identifying, for a particular user, acharacteristic of an assigned access right and information about aresource associated with the access right.

One or more data structures in a relational data structure may reflectwhether particular access rights have been assigned or remain available.This data may be based on data received from a catalog system 342 thatmonitors and tracks statuses of resource access rights. Catalog system342 can include one or more catalog processors (e.g., included in one ormore server farms, which may be geographically separated). Catalogprocessors can be configured to generate status-update requestcommunications to be sent to one or more access assignment systemsand/or intermediate systems and/or to receive status-updatecommunications from one or more access assignment systems and/orintermediate systems. A status-update communication can, for example,identify an access right and/or resource and indicate an assignment ofthe access right. For example, a status-update communication canindicate that a particular access right has been assigned and is thus nolonger available. In some instances, a status-update communicationidentifies assignment details, such as a user, profile and/or userdevice associated with an access-right assignment; a time that theassignment was made; and/or a price associated with the assignment.

In some instances, a status update is less explicit. For example, acommunication may identify an access right and/or resource and request afinal authorization of an assignment of the access right. Catalog system342 can then verify that the access right is available for assignment(e.g., and that a request-associated system or entity is authorized tocoordinate the assignment) and can transmit an affirmative response.Such a communication exchange can indicate (in some instances) that theaccess right is assigned and unavailable for other assignment.

In some instances, catalog system 342 can also be integrated with anon-intermediate access assignment system, such that it can directlydetect assignments. For example, an integrated access assignment systemcan coordinate a message exchange with a user device, can query acatalog data store to identify available access rights and canfacilitate or trigger a status-change of an access right to reflect anassignment (e.g., upon having received all required information.

Whether a result of a direct assignment detection or a status updatefrom an intermediate system, a database engine of catalog system 342 canmanage one or more data stores so as to indicate a current status ofeach of a set of access rights for a resource. The one or more datastores may further identify any assignment constraints. For example,particular access rights may be earmarked so as to only allow one ormore particular intermediate systems to trigger a change to the accessrights' status and/or to assign the access rights.

The database engine can include a digital asset management (DAM) engineto receive, transform (e.g., annotate, reformat, introduce a schema,etc.) status-update communications, and identify other data (e.g., anidentifier of an assigning system and/or a time at which a communicationwas received) to associate with a status update (e.g., an assignment).Therefore, the DAM engine can be configured to prepare storage-updatetasks so as to cause a maintained data store to reflect a recent datachange.

Further, the DAM engine can facilitate handling of data-store queries.For example, a status-request communication or authorization-requestcommunication can be processed to identify variables and/or indices touse to query a data store. A query can then be generated and/or directedto a data store based on the processing. The DAM engine can relay (e.g.,and, potentially, perform intermediate processing to) a query result toa request-associate system.

The database engine can also include a conflict engine, which can beconfigured to access and implement rules indicating how conflicts are tobe handled. For example, catalog system 342 may receive multiplerequests within a time period requesting an assignment authorization (ora hold) for a particular access right. A rule may indicate that a firstrequest is to receive priority, that a request associated with a morehighly prioritized requesting system (e.g., intermediate system) is tobe prioritized, that a request associated with a relatively high (orlow) quantity of access rights identified in the request for potentialassignment are to be prioritized, etc.

The database engine can further include a storage engine configured tomanage data access and/or data updates (e.g., modifying existing data oradding new data). The data managed by and/or accessible to the storageengine can be included in one or more data stores. The data stores caninclude, for example, distributed, non-distributed, virtual,non-virtual, local and/or remote data stores. The data stores caninclude, for example, a relational, non-relational, object, non-object,document and/or non-document data store. Part or all of a data store caninclude a shadow data store, that shadows data from another data store.Part or all of a data store can include an authoritative data store thatis (e.g., directly and/or immediately) updated with access-rightassignment changes (e.g., such that a primary or secondary accessassignment system updates the data store as part of an access-rightassignment process, rather than sending a post-hoc status-updatecommunication reflecting the assignment). In some instances, a datastore an authoritative data store identifies a status for each of a set(e.g., or all) of access rights for a given resource. Should there beany inconsistency between an authoritative data store and another datastore (e.g., at an intermediate system), system 300 can be configuredsuch that the authoritative data store is controlling.

System 300 can further include a replication system 343. Replicationsystem 343 can include one or more replication processors configured toidentify new or modified data, to identify one or more data storesand/or location at which to store the new or modified data and/or tocoordinate replication of the data. In some instances, one or more ofthese identifications and/or coordination can be performed using areplication rule. For example, a replication rule may indicate thatreplication is to be performed in a manner biased towards storingreplicated data at a data store geographically separated from anotherdata store storing the data.

A data duplicator can be configured to read stored data and generate oneor more write commands so as to store the data at a different datastore. A controller can manage transmitting write commands appropriatelyso as to facilitate storing replicated data at identified data stores.Further, a controller can manage data stores, such as a distributedmemory or distributed shared memory, to ensure that a currently activeset of data stores includes a target number of replications of data.

Accordingly, web-server system 318 can interact with user device 310 toidentify available access rights and to collect information needed toassign an access right. Web-server system 318 can interact with SQLsystem 341 so as to retrieve data about particular resources and/oraccess rights so as to configure web data (e.g., via dynamic webpages orscripts) to reflect accurate or semi-accurate information and/orstatuses. SQL system 341 can use relational data stores to quicklyprovide such data. Meanwhile, catalog system 342 may manage one or morenon-relational and/or more comprehensive data stores may be tasked withmore reliably and quickly tracking access-right statuses andassignments. The tracking may include receiving status updates (e.g.,via a push or pull protocol) from one or more intermediate systemsand/or by detecting assignment updates from non-intermediate systems,such as an integrated access assignment system and/or SQL system 341.Catalog system 342 may provide condensed status updates (e.g.,reflecting a binary indication as to whether an access right isavailable) to SQL system 341 periodically, at triggered times and/or inresponse to a request from the SQL system. A replication system 343 canfurther ensure that data is replicated at multiple data stores, so as toimprove a reliability and speed of system 300.

It will be appreciated that various parts of system 300 can begeographically separated. For example, each of user device 310,intermediate system 330, web-server system 318, SQL system 341, catalogsystem 342 and replication 343 may be located in different geographiclocations (e.g., different cities, states or countries).

FIG. 4 illustrates example components of a device 400, such as a clientdevice (e.g., client agent device 140, client register 150 and/or clientpoint device 160), an intermediate system (e.g., intermediate system130) and/or an access management system (e.g., access management system120) according to an embodiment of the invention.

The components can include one or more modules that can be installed ondevice 400. Modules can include some or all of the following: a networkinterface module 402 (which can operate in a link layer of a protocolstack), a message processor module 404 (which can operate in an IP layerof a protocol stack), a communications manager module 406 (which canoperate in a transport layer of a protocol stack), a communicationsconfigure module 408 (which can operate in a transport and/or IP layerin a protocol stack), a communications rules provider module 410 (whichcan operate in a transport and/or IP layer in a protocol stack),application modules 412 (which can operate in an application layer of aprotocol stack), a physical access control module 432 and one or moreenvironmental sensors 434.

Network interface module 402 receives and transmits messages via one ormore hardware components that provide a link-layer interconnect. Thehardware component(s) can include, for example, RF antenna 403 or a port(e.g., Ethernet port) and supporting circuitry. In some embodiments,network interface module 402 can be configured to support wirelesscommunication, e.g., using Wi Fi (IEEE 802.11 family standards),Bluetooth® (a family of standards promulgated by Bluetooth SIG, Inc.),BLE, or near-field communication (implementing the ISO/IEC 18092standards or the like).

RF antenna 403 can be configured to convert electric signals into radioand/or magnetic signals (e.g., to radio waves) to transmit to anotherdevice and/or to receive radio and/or magnetic signals and convert themto electric signals. RF antenna 403 can be tuned to operate within aparticular frequency band. In some instances, a device includes multipleantennas, and the antennas can be, for example, physically separated. Insome instances, antennas differ with respect to radiation patterns,polarizations, take-off angle gain and/or tuning bands. RF interfacemodule 402 can include one or more phase shifters, filters, attenuators,amplifiers, switches and/or other components to demodulate receivedsignals, coordinate signal transmission and/or facilitate high-qualitysignal transmission and receipt.

In some instances, network interface module 402 includes a virtualnetwork interface, so as to enable the device to utilize an intermediatedevice for signal transmission or reception. For example, networkinterface module 402 can include VPN software.

Network interface module 402 and one or more antennas 403 can beconfigured to transmit and receive signals over one or more connectiontypes. For example, network interface module 402 and one or moreantennas 403 can be configured to transmit and receive WiFi signals,cellular signals, Bluetooth signals, Bluetooth Low Energy (BLE) signals,Zigbee signals, or Near-Field Communication (NFC) signals.

Message processor module 404 can coordinate communication with otherelectronic devices or systems, such as one or more servers or a userdevice. In one instance, message processor module 404 is able tocommunicate using a plurality of protocols (e.g., any known, futureand/or convenient protocol such as, but not limited to, XML, SMS, MMS,and/or email, etc.). Message processor module 404 may further optionallyserialize incoming and/or outgoing messages and facilitate queuing ofincoming and outgoing message traffic.

Message processor module 404 can perform functions of an IP layer in anetwork protocol stack. For example, in some instances, messageprocessor module 404 can format data packets or segments, combine datapacket fragments, fragment data packets and/or identify destinationapplications and/or device addresses. For example, message processormodule 404 can defragment and analyze an incoming message to determinewhether it is to be forwarded to another device and, if so, can addressand fragment the message before sending it to the network interfacemodule 402 to be transmitted. As another example, message processormodule 404 can defragment and analyze an incoming message to identify adestination application that is to receive the message and can thendirect the message (e.g., via a transport layer) to the application.

Communications manager module 406 can implement transport-layerfunctions. For example, communications manager module 406 can identify atransport protocol for an outgoing message (e.g., transmission controlprotocol (TCP) or user diagram protocol (UDP)) and appropriatelyencapsulate the message into transport protocol data units. Messageprocessor module 404 can initiate establishment of connections betweendevices, monitor transmissions failures, control data transmission ratesand monitoring transmission quality. As another example, communicationsmanager module 406 can read a header of an incoming message to identifyan application layer protocol to receive the message's data. The datacan be separated from the header and sent to the appropriateapplication. Message processor module 404 can also monitor the qualityof incoming messages and/or detect out of order incoming packets.

In some instances, characteristics of message-receipt ormessage-transmission quality can be used to identify a health status ofan established communications link. In some instances, communicationsmanager module 406 can be configured to detect signals indicating thehealth status of an established communications link (e.g., a periodicsignal from the other device system, which if received without dropouts,indicates a healthy link).

In some instances, a communication configurer module 408 is provided totrack attributes of another system so as to facilitate establishment ofa communication session. In one embodiment, communication configurermodule 408 further ensures that inter-device communications areconducted in accordance with the identified communication attributesand/or rules. Communication configurer module 408 can maintain anupdated record of the communication attributes of one or more devices orsystems. In one embodiment, communications configurer module 408 ensuresthat communications manager module 406 can deliver the payload providedby message processor module 404 to the destination (e.g., by ensuringthat the correct protocol corresponding to the client system is used).

A communications rules provider module 410 can implement one or morecommunication rules that relate to details of signal transmissions orreceipt. For example, a rule may specify or constrain a protocol to beused, a transmission time, a type of link or connection to be used, adestination device, and/or a number of destination devices. A rule maybe generally applicable or conditionally applicable (e.g., only applyingfor messages corresponding to a particular app, during a particular timeof day, while a device is in a particular geographical region, when ausage of a local device resource exceeds a threshold, etc.). Forexample, a rule can identify a technique for selecting between a set ofpotential destination devices based on attributes of the set ofpotential destination devices as tracked by communication configuremodule 408. To illustrate, a device having a short response latency maybe selected as a destination device. As another example, communicationsrules provider 410 can maintain associations between various devices orsystems and resources. Thus, messages corresponding to particularresources can be selectively transmitted to destinations having accessto such resources.

A variety of application modules 412 can be configured to initiatemessage transmission, process incoming transmissions, facilitateselective granting of resource access, facilitate processing of requestsfor resource access, and/or performing other functions. In the instancedepicted in FIG. 4, application modules 412 include an auto-updatermodule 414, a resource access coordinator module 416, and/or a codeverification module 418.

Auto-updater module 414 automatically updates stored data and/or agentsoftware based on recent changes to resource utilization, availabilityor schedules and/or updates to software or protocols. Such updates canbe pushed from another device (e.g., upon detecting a change in aresource availability or access permit) or can be received in responseto a request sent by device 400. For example, device 400 can transmit asignal to another device that identifies a particular resource, and aresponsive signal can identify availabilities of access to the resource.As another example, device 400 can transmit a signal that includes anaccess access-enabling code, and a responsive signal can indicatewhether the code is applicable for access of a particular resourceand/or is valid.

In some instances, auto-updater module 414 is configured to enable theagent software to understand new, messages, commands, and/or protocols,based on a system configuration/change initiated on another device.Auto-updater module 414 may also install new or updated software toprovide support and/or enhancements, based on a system configurationchange detected on device 400. System configuration changes that wouldnecessitate changes to the agent software can include, but are notlimited to, a software/hardware upgrade, a security upgrade, a routerconfiguration change, a change in security settings, etc. For example,if auto-updater module 414 determines that a communication link withanother device has been lost for a pre-determined amount of time,auto-updater module 414 can obtain system configuration information tohelp re-establish the communication link. Such information may includenew settings/configurations on one or more hardware devices or new orupgraded software on or connected to device 400. Thus, auto-updatermodule 414 can detect or be informed by other software when there is anew version of agent software with additional functionality and/ordeficiency/bug corrections or when there is a change with respect to thesoftware, hardware, communications channel, etc.), and perform updatesaccordingly.

Based on the newly obtained system configuration for device 400,auto-updater module 414 can cause a new communication link to bere-established with another device. In one embodiment, uponestablishment of the communication link, system configurationinformation about device 400 can also be provided to another device tofacilitate the connection to or downloading of software to device 400.

In one embodiment, when a poor health signal is detected by anotherdevice (e.g., when the health signal is only sporadically received butthe communication link is not necessarily lost), the other device cansend a command to auto-updater module 414 to instruct auto-updatermodule 414 to obtain system configuration information about device 400.The updated system configuration information may be used in an attemptto revive the unhealthy communications link (e.g., by resending aresource request). For example, code can utilize appropriate systemcalls for the operating system to fix or reestablish communications. Byway of example and not limitation, model and driver information isoptionally obtained for routers in the system in order querying them. Byway of further example, if the code determines that a new brand ofrouter has been installed, it can adapt to that change, or to the changein network configuration, or other changes.

Instead or in addition, the host server (e.g., via communicationsmanager 406) can send specific instructions to auto-updater module 414to specify tests or checks to be performed on device 400 to determinethe changes to the system configurations (e.g., by automaticallyperforming or requesting an inventory check of system hardware and/orsoftware). For example, the components involved in the chain of hopsthrough a network can be queried and analyzed. Thus, for example, if anew ISP (Internet service provider) is being used and the managementsystem traffic is being filtered, or a new router was installed and thesoftware needs to change its configuration, or if someone made a changeto the operating system that affects port the management system is usingto communicate, the management system (or operator) can communicate withthe ISP, change it back, or choose from a new available port,respectively.

The specific tests may be necessary to help establish the communicationlink, if, for example, the automatic tests fail to provide sufficientinformation for the communication link to be re-established, ifadditional information is needed about a particular configurationchange, and/or if the client system is not initially supported by theauto-updater module 414, etc.

Auto-updater module 414 can also receive signals identifying updatespertaining to current or future availability of resources and/or accesspermits. Based on the signals, auto-updater module 414 can modify, addto or delete stored data pertaining to resource availabilities, resourceschedules and/or valid access permits. For example, upon receiving anupdate signal, auto-updater 414 can modify data stored in one or moredata stores 422, such as a profile data store 424, resourcespecification data store 426, resource status data store 428 and/oraccess-enabling code data store 430.

Profile data store 424 can store data for entities, such asadministrators, intermediate-system agents and/or users. The profiledata can include login information (e.g., username and password),identifying information (e.g., name, residential address, phone number,email address, age and/or gender), professional information (e.g.,occupation, affiliation and/or professional position), and preferences(e.g., regarding resource types, entities, access right locations,and/or resource types). The profile data can also or alternativelyinclude technical data, such a particular entity can be associated withone or more device types, IP addresses, browser identifier and/oroperating system identifier).

Resource specification data store 426 can store specification datacharacterizing each of one or more resources. For example, specificationdata for a resource can include a processing power, available memory,operating system, compatibility, device type, processor usage, powerstatus, device model, number of processor cores, types of memories, dateand time of availability, a resource entity, and/or a spatial region ofthe resource. Specification data can further identify, for example, acost for each of one or more access rights.

Resource status data store 428 can store status data reflecting whichresources are available (or unavailable), thereby indicating whichresources have one or more open assignments. In some instances, thestatus data can include schedule information about when a resource isavailable. Status data can include information identifying an entity whorequested, automatically and/or tentatively assigned or was assigned aresource. In some instances, status information can indicate that aresource is being held or automatically and/or tentatively assigned andmay identify an entity associated with the hold and/or a time at whichthe hold or reservation will be enabled to be queried.

Access-enabling code data store 430 can store access-enabling code datathat includes one or more codes and/or other information that can beused to indicate that an entity is authorized to use, have or receive aresource. An access-enabling code can include, for example, a numericstring, an alphanumeric string, a text string, a 1-dimensional code, a2-dimensional code, a barcode, a quick response (QR) code, an image, astatic code and/or a temporally dynamic code. An access-enabling codecan be, for example, unique across all instances, resource types and/orentities. For example, access-enabling codes provided in association foraccess rights to a particular resource can be unique relative to eachother. In some instances, at least part of a code identifies a resourceor specification of a resource.

One or more of data stores 424, 426, 428, and 430 can be a relationaldata store, such that elements in one data store can be referencedwithin another data store. For example, resource status data store 428can associate an identifier of a particular access right with anidentifier of a particular entity. Additional information about theentity can then be retrieved by looking up the entity identifier inprofile data store 424.

Updates to data stores 424, 426, 428, and 430 facilitated and/orinitiated by auto-updater module 414 can improve cross-device dataconsistency. Resource access coordinator module 416 can coordinateresource access by, for example, generating and distributingidentifications of resource availabilities; processing requests forresource access; handling competing requests for resource access; and/orreceiving and responding to resource-offering objectives.

FIG. 5 illustrates example components of resource access coordinatormodule 416 that may operate, at least in part, at an access managementsystem (e.g., access management system) according to an embodiment ofthe present disclosure. A resource specification engine 502 can identifyone or more available resources. For example, resource specificationengine 502 can detect input that identifies a current or futureavailability of a new resource.

Resource specification engine 502 can identify one or morespecifications of each of one or more resources. A specification caninclude an availability time period. For example, resource specificationengine 502 can determine that a resource is available, for example, at aparticular date and time (e.g., as identified based on input), for atime period (e.g., a start to end time), as identified in the input,and/or from a time of initial identification until another inputindicating that the resource is unavailable is detected. A specificationcan also or alternatively include a location (e.g., a geographiclocation and/or spatial region) of the resource. A specification canalso or alternatively include one or more parties associated with theresource. Resource specification engine 502 can store the specificationsin association with an identifier of the resource in resourcespecifications data store 426.

A resource-access allocation engine 504 can allocate access rights forindividual resources. An access right can serve to provide an associatedentity with the right or a priority to access a resource. Because (forexample) association of an access right with an entity can, in someinstances, be conditioned on one or more steps of an assignment processor authorization thereof, an allocated access right can be initiallyunassociated with particular entities (e.g., users). For example, anallocated right can correspond to one or more access characteristics,such as an processor identifier, a usage time, a memory allocation,and/or a geographic location. For an allocated access right,resource-access allocation engine 504 can store an identifier of theright in resource statuses data store 428 in association with anidentifier for the resource and an indication that it has not yet beenassigned to a particular entity.

A communication engine 506 can facilitate communicating the availabilityof the resource access rights to users. In some instances, a publisherengine 508 generates a presentation that identifies a resource andindicates that access rights are available. Initially or in response touser interaction with the presentation, the presentation can identifyaccess characteristics about available access rights. The presentationcan include, for example, a chart that identifies available accessrights for an event. Publisher engine 508 can distribute thepresentation via, for example, a website, app page, email and/ormessage. The presentation can be further configured to enable a user torequest assignments of one or more access rights.

In some instances, an intermediate system coordination engine 510 canfacilitate transmission of information about resource availability(e.g., resource specifications and characteristics of resource-accessrights) to one or more intermediate systems (e.g., by generating one ormore messages that include such information and/or facilitatingpublishing such information via a website or app page). Each of the oneor more intermediate systems can publish information about the resourceand accept requests for resource access. In some instances, intermediatesystem coordination engine 510 identifies different access rights asbeing available to individual intermediate systems to coordinateassignment. For example, access rights for Section 1 may be provided fora first intermediate system to assign, and access rights for Section 2may be provided to a second intermediate system to assign.

In some instances, overlapping access rights are made available tomultiple intermediate systems to coordinate assignments. For example,some or all of a first set of resource rights (e.g., corresponding to asection) may be provided to first and second intermediate systems. Insuch instances, intermediate system coordination engine 510 can respondto a communication from a first intermediate system indicating that arequest has been received (e.g., and processed) for an access right inthe set) by sending a notification to one or more other intermediatesystems that indicates that the access right is to be at leasttemporarily (or entirely) made unavailable.

Intermediate system coordination engine 510 can monitor communicationchannels with intermediate systems to track the health and security ofthe channel. For example, a healthy connection can be inferred whenscheduled signals are consistently received. Further, intermediatesystem coordination engine 510 can track configurations of intermediatesystems (e.g., via communications generated at the intermediate systemsvia a software agent that identifies such configurations) so as toinfluence code generation, communication format, and/or provisions oraccess rights.

Thus, either via a presentation facilitated by publisher engine 508(e.g., via a web site or app page) or via communication with anintermediate system, a request for assignment of an access right can bereceived. A request management engine 512 can process the request.Processing the request can include determining whether all otherrequired information has been received, such as user-identifyinginformation (e.g., name), access-right identifying information (e.g.,identifying a resource and/or access-right characteristic) user contactinformation, and/or user device information (e.g., type of device,device identifier, and/or IP address).

When all required information has not been received, request managementengine 512 can facilitate collection of the information (e.g., via aninterface, app page or communication to an intermediate system). Requestmanagement engine 512 can also or alternatively execute or facilitatethe execution of the assignment process, which includes one or moresteps for completing an assignment of an access right to a user deviceor user profile. For example, publisher engine 508 may receive datainputted by the user via an interface, and request management engine 512can request authorization to complete the assignment process. In someinstances, request management engine 512 retrieves data from a userprofile. For example, publisher engine 508 may indicate that a requestfor an access right has been received while a user was logged into aparticular profile. Request management engine 512 may then retrieve, forexample, contact information, device information, and/or preferencesinformation associated with the profile from profile data store 424.

In some instances, request management engine 512 prioritizes requests,such as requests for overlapping, similar or same access rights receivedwithin a defined time period. The prioritization can be based on, forexample, times at which requests were received (e.g., prioritizingearlier requests), a request parameter (e.g., prioritizing requests fora higher or lower number of access rights above others), whetherrequests were received via an intermediate system (e.g., prioritizingsuch requests lower than others), intermediate systems associated withrequests, whether requests were associated with users having establishedprofiles, and/or whether requests were associated with inputs indicativeof a bot initiating the request (e.g., shorter inter-click intervals,failed CAPTCHA tests).

Upon determining that required information has been received andrequest-processing conditions have been met, request management engine512 can forward appropriate request information to a resource schedulingengine 514. For a request, resource scheduling engine 514 can queryresource status data store 428 to identify access rights matchingparameters of the request.

In some instances, the request has an access-right specificity matchinga specificity at which access rights are assigned. In some instances,the request is less specific, and resource scheduling engine 514 canthen facilitate an identification of particular rights to assign. Forexample, request management engine 512 can facilitate a communicationexchange by which access right characteristics matching the request areidentified, and a user is allowed to select particular rights. Asanother example, request management engine 512 can itself select fromamongst matching access rights based on a defined criterion (e.g., bestsummed or averaged access-right ranking, pseudo-random selection, or aselection technique identified based on user input).

Upon identifying appropriately specific access rights, resourcescheduling engine 514 can update resource status data store 428 so as toplace the access right(s) on hold (e.g., while obtaining userconfirmation) and/or to change a status of the access right(s) toindicate that they have been assigned (e.g., immediately, uponcompleting an assignment process or upon receiving user confirmation).Such assignment indication may associate information about the user(e.g., user name, device information, phone number and/or email address)and/or assignment process (e.g., identifier of any intermediate systemand/or assignment date and time) with an identifier of the accessright(s).

For individual assigned access rights, an encoding engine 516 cangenerate an access-enabling code. The access-enabling code can include,for example, an alphanumeric string, a text string, a number, a graphic,a code (e.g., a 1-dimensional or 2-dimensional code), a static code, adynamic code (e.g., with a feature depending on a current time, currentlocation or communication) and/or a technique for generating the code(e.g., whereby part of the code may be static and part of the code maybe determined using the technique). The code may be unique across allaccess rights, all access rights for a given resource, all access rightsassociated with a given location, all access rights associated with agiven time period, all resources and/or all users. In some instances, atleast part of the code is determined based on or is thereafterassociated with an identifier of a user, user device information, aresource specification and/or an access right characteristic.

In various embodiments, the code may be generated prior to allocatingaccess rights (e.g., such that each of some or all allocated accessrights are associated with an access-enabling code), prior to or whileassigning one or more access right(s) responsive to a request (e.g.,such that each of some or all assigned access rights are associated withan access-enabling code), at a prescribed time, and/or when the deviceis at a defined location and/or in response to user input. The code maybe stored at or availed to a user device. In various instances, at theuser device, an access-enabling code may be provided in a manner suchthat it is visibly available for user inspection or concealed from auser. For example, a physical manifestation of an access right may be adocument with an access code, and a copy of this document may betransmitted to a user device, or an app on the user device can transmita request with a device identifier for a dynamic code.

Encoding engine 516 can store the access-enabling codes inaccess-enabling code data store 430. Encoding engine 516 can also oralternatively store an indication in profile data store 424 that theaccess right(s) have been assigned to the user. It will again beappreciated that data stores 424, 426, 428, and 430 can be relationaland/or linked, such that, for example, an identification of anassignment can be used to identify one or more access rights, associatedaccess-enabling code(s) and/or resource specifications.

Resource scheduling engine 514 can facilitate one or more transmissionsof data pertaining to one or more assigned access rights to a device ofa user associated with the assignment and/or to an intermediate systemfacilitating the assignment and/or having transmitted a correspondingassignment request. The data can include an indication that accessrights have been assigned and/or details as to which rights have beenassigned. The data can also or alternatively include access-enablingcodes associated with assigned access rights.

While FIG. 5 depicts components of resource access coordinator module516 that may be present on an access management system 120, it will beappreciated that similar or complementary engines may be present onother systems. For example, a communication engine on a user device canbe configured to display presentations identifying access rightavailability, and a request management engine on a user device can beconfigured to translate inputs into access-right requests to send to anintermediate system or access management system.

Returning to FIG. 4, code verification module 418 (e.g., at a userdevice or client device) can analyze data to determine whether anaccess-enabling code is generally valid and/or valid for a particularcircumstance. The access-enabling code can include one that is receivedat or detected by device 400. The analysis can include, for example,determining whether all or part of the access-enabling code matches onestored in access-enabling code data store 430 or part thereof, whetherthe access-enabling code has previously been applied, whether all orpart of the access-enabling code is consistent with itself or otherinformation (e.g., one or more particular resource specifications, acurrent time and/or a detected location) as determined based on aconsistency analysis and/or whether all or part of the access-enablingcode has an acceptable format.

For example, access-enabling code data store 430 can be organized in amanner such that access-enabling codes for a particular resource, date,resource group, client, etc. can be queried to determine whether anysuch access-enabling codes correspond to (e.g. match) one beingevaluated, which may indicate that the code is verified. Additionalinformation associated with the code may also or alternatively beevaluated. For example, the additional information can indicate whetherthe code is currently valid or expired (e.g., due to a previous use ofthe code).

As another example, a portion of an access-enabling code can include anidentifier of a user device or user profile, and code verificationmodule 418 can determine whether the code-identified device or profilematches that detected as part of the evaluation. To illustrate, device400 can be a client device that electronically receives a communicationwith an access-enabling code from a user device. The communication canfurther include a device identifier that identifies, for example, thatthe user device is a particular type of smartphone. Code verificationmodule 418 can then determine whether device-identifying information inthe code is consistent with the identified type of smartphone.

As yet another example, code verification module 418 can identify a codeformat rule that specifies a format that valid codes are to have. Toillustrate, the code format rule may identify a number of elements thatare to be included in the code or a pattern that is to be present in thecode. Code verification module 418 can then determine that a code is notvalid if it does not conform to the format.

Verification of an access-enabling code can indicate that access to aresource is to be granted. Conversely, determining that a code is notverified can indicate that access to a resource is to be limited orprevented. In some instances, a presentation is generated (e.g., andpresented) that indicates whether access is to be granted and/or aresult of a verification analysis. In some instances, access grantingand/or limiting is automatically affected. For example, upon a codeverification, a user device and/or user may be automatically permittedto access a particular resource. Accessing a resource may include, forexample, using a computational resource, possessing an item, receiving aservice, entering a geographical area, and/or attending an event (e.g.,generally or at a particular location).

Verification of an access-enabling code can further trigger amodification to access-enabling code data store 430. For example, a codethat has been verified can be removed from the data store or associatedwith a new status. This modification may limit attempts to use a samecode multiple times for resource access.

A combination of modules 414, 416, 418 comprise a secure addressableendpoint agent 420 that acts as an adapter and enables cross-deviceinterfacing in a secure and reliable manner so as to facilitateallocation of access-enabling codes and coordinate resource access.Secure addressable endpoint agent 420 can further generate a healthsignal that is transmitted to another device for monitoring of a statusof a communication channel. The health signal is optionally a shortmessage of a few bytes or many bytes in length that may be transmittedon a frequent basis (e.g., every few milliseconds or seconds). Acommunications manager 406 on the receiving device can then monitors thehealth signal provided by the agent to ensure that the communicationlink between the host server and device 400 is still operational.

In some instances, device 400 can include (or can be in communicationwith) a physical access control 432. Physical access control 432 caninclude a gating component that can be configured to provide a physicalbarrier towards accessing a resource. For example, physical accesscontrol 432 can include a turnstile or a packaging lock.

Physical access control 432 can be configured such that it can switchbetween two modes, which differ in terms of a degree to which useraccess to a resource is permitted. For example, a turnstile may have alocked mode that prevents movement of an arm of the turnstile and anunlocked mode that allows the arm to be rotated. In some instances, adefault mode is the mode that is more limiting in terms of access.

Physical access control 432 can switch its mode in response to receivingparticular results from code verification module 418. For example, uponreceiving an indication that a code has been verified, physical accesscontrol 432 can switch from a locked mode to an unlocked mode. It mayremain in the changed state for a defined period of time or until anaction or event is detected (e.g., rotation of an arm).

Device 400 can also include one or more environmental sensors 434.Measurements from the sensor can processed by one or more applicationmodules. Environmental sensor(s) 434 can include a global positioningsystem (GPS) receiver 435 that can receive signals from one or more GPSsatellites. A GPS chipset can use the signals to estimate a location ofdevice 400 (e.g., a longitude and latitude of device 400). The estimatedlocation can be used to identify a particular resource (e.g., one beingoffered at or near the location at a current or near-term time). Theidentification of the particular resource can be used, for example, toidentify a corresponding (e.g., user-associated) access-enabling code orto evaluate an access-enabling code (e.g., to determine whether itcorresponds to a resource associated with the location).

The estimated location can further or alternatively be used to determinewhen to perform a particular function. For example, at a user device,detecting that the device is in or has entered a particular geographicalregion (e.g., is within a threshold distance from a geofence perimeteror entrance gate) can cause the device to retrieve or request anaccess-enabling code, conduct a verification analysis of the code and/ortransmit the code to a client device.

It will be appreciated that environmental sensor(s) 434 can include oneor more additional or alternative sensors aside from GPS receiver 435.For example, a location of device 400 can be estimated based on signalsreceived by another receive from different sources (e.g., base stations,client point devices or Wi Fi access points). As another example, anaccelerometer and/or gyroscope can be provided. Data from these sensorscan be used to infer when a user is attempting to present anaccess-enabling code for evaluation.

It will also be appreciated that the components and/or engines depictedin figures herein are illustrative, and a device need not include eachdepicted component and/or engine and/or can include one or moreadditional components and/or engines. For example, a device can alsoinclude a user interface, which may include a touch sensor, keyboard,display, camera and/or speakers. As another example, a device caninclude a power component, which can distribute power to components ofthe device. The power component can include a battery and/or aconnection component for connecting to a power source. As yet anotherexample, a module in the application layer can include an operatingsystem. As still another example, an application-layer control processormodule can provide message processing for messages received from anotherdevice. The message processing can include classifying the message androuting it to the appropriate module. To illustrate, the message can beclassified as a request for resource access or for an access-enablingcode, an update message or an indication that a code has been redeemedor verified. The message processing module can further convert a messageor command into a format that can interoperate with a target module.

It will further be appreciated that the components, modules and/oragents could be implemented in one or more instances of software. Thefunctionalities described herein need not be implemented in separatemodules, for example, one or more functions can be implemented in onesoftware instance and/or one software/hardware combination. Othercombinations are similarly be contemplated.

Further yet, it will be appreciated that a storage medium (e.g., usingmagnetic storage media, flash memory, other semiconductor memory (e.g.,DRAM, SRAM), or any other non-transitory storage medium, or acombination of media, and can include volatile and/or non-volatilemedia) can be used to store program code for each of one or more of thecomponents, modules and/or engines depicted in FIGS. 4 and 5 and/or tostore any or all data stores depicted in FIG. 4 or described withreference to FIGS. 4 and/or 5. Any device or system disclosed herein caninclude a processing subsystem for executing the code. The processingsystem can be implemented as one or more integrated circuits, e.g., oneor more single-core or multi-core microprocessors or microcontrollers,examples of which are known in the art.

FIG. 6 illustrates a flowchart of an embodiment of a process 600 forassigning access rights for resources. Process 600 can be performed byan access management system, such as access management system 120.Process 600 begins at block 605 where resource specification engine 502identifies one or more specifications for a resource. The specificationscan include, for example, a time at which the resource is to beavailable, a location of the resource, a capacity of the resourcesand/or one or more entities (e.g., performing entities) associated withthe resource.

At block 610, resource-access allocation engine 504 allocates a set ofaccess rights for the resource. In some instances, each of at least someof the access rights corresponds to a different access parameter, suchas a different location assignment. Upon allocation, each of some or allof the access rights may have a status as available. A subset of the setof access rights can be immediately (or at a defined time) assigned orreserved according to a base assignment or reservation rule (e.g.,assigning particular access rights to particular entities, who may beinvolved in or related to provision of the resource and/or who haverequested or been assigned a set of related access rights.

At block 615, communication engine 506 transmits the resourcespecifications and data about the access rights. The transmission canoccur in one or more transmissions. The transmission can be to, forexample, one or more user devices and/or intermediate systems. In someinstances, a notification including the specifications and access-rightdata is transmitted, and in some instances, a notification can begenerated at a receiving device based on the specifications andaccess-right data. The notification can include, for example, a websitethat identifies a resource (via, at least in part, its specifications)and indicates that access rights for the resource are available forassignment. The notification can include an option to request assignmentof one or more access rights.

At block 620, request management engine 512 receives a request for oneor more access rights to be assigned to a user. The request can, forexample, identify particular access rights and/or access parameters. Therequest can include or be accompanied by other information, such asidentifying information. In some instances, the access management systemcan use at least some of such information to determine whether anassignment process has been completed. In some instances, the request isreceived via an intermediate system that has already handled suchauthorization.

At block 625, resource scheduling engine 514 assigns the requested oneor more access rights to the user. The assignment can be conditioned onreceipt of all required information, confirmation that the accessright(s) have remained available for assignment, determining using datacorresponding to the request that a bot-detection condition is notsatisfied and/or other defined conditions. Assignment of the accessright(s) can include associating an identifier of each of the one ormore rights with an identifier of a user and/or assignment and/orchanging a status of the access right(s) to assigned. Assignment of theaccess right(s) can result in impeding or preventing other users fromrequesting the access right(s), being assigned the access right(s)and/or being notified that the access right(s) are available forassignment. Assignment of the access right(s) can, in some instances,trigger transmission of one or more communications to, for example, oneor more intermediate systems identifying the access right(s) andindicating that they have been assigned and/or with an instruction tocease offering the access rights.

At block 630, encoding engine 516 generates an access-enabling code foreach of the one or more access rights. The code can be generated, forexample, as part of the assignment, as part of the allocation orsubsequent to the assignment (e.g., upon detecting that a user isrequesting access to the resource). Generating an access-enabling codecan include applying a code-generation technique, such on one thatgenerates a code based on a characteristic of a user, user device,current time, access right, resource, intermediate system or othervariable. The access-enabling code can include a static code that willnot change after it has been initially generated or a dynamic code thatchanges in time (e.g., such that block 630 can be repeated at varioustime points).

At block 635, communication engine 506 transmits a confirmation of theassignment and the access-enabling code(s) in one or more transmissions.The transmission(s) may be sent to one or more devices, such as a userdevice having initiated the request from block 620, a remote server oran intermediate system having relayed the request from block 620.

Referring to FIG. 7A, an embodiment of a site system 180 is shown inrelation to mobile devices 724-n, Network Attached Storage (NAS) 750,site network 716 and the Internet 728. In some embodiments, for userslocated within the spatial region of the resource, site network 716 andsite system 180 provide content, services and/or interactive engagementusing mobile devices 724. Connections to site system 180 and sitenetwork 716 can be established by mobile devices 724 connecting toaccess points 720. Mobile devices 724 can be a type of end user device110 that is portable, e.g., smartphones, mobile phones, tablets, and/orother similar devices.

Site network 716 can have access to content (information about theresource, videos, images, etc.) held by NAS 750. Additionally, asdescribed herein, content can be gathered from users both before andduring the time period the resource is accessible. By connecting to sitenetwork 716, mobile device 724 can send content for use by site system180 or display content received from NAS 750.

Referring to FIG. 7B, another embodiment of a site system 180 is shownin relation to mobile devices 724-n, Network Attached Storage (NAS) 750,site network 716 and the Internet 728, in an embodiment. FIG. 7Badditionally includes phone switch 740. In some embodiments, phoneswitch 740 can be a private cellular base station configured to spoofthe operation of conventionally operated base stations. Using phoneswitch 740 at an event site allows site system 180 to provide additionaltypes of interactions with mobile devices 724. For example, without anysetup or configuration to accept communications from site controller712, phone switch 740 can cause connected mobile devices 724 to ringand, when answered, have an audio or video call be established. Whenused with other embodiments described herein, phone switch 740 canprovide additional interactions. For example, some embodiments describedherein use different capabilities of mobile devices 724 to cause masssounds and/or establish communications with two or more people. Bycausing phones to ring and by establishing cellular calls, phone switchcan provide additional capabilities to these approaches.

FIG. 8 shows a block diagram of user device 110 according to anembodiment. User device 110 includes a handheld controller 810 that canbe sized and shaped so as enable the controller and user device 110 in ahand. Handheld controller 810 can include one or more user-deviceprocessors that can be configured to perform actions as describedherein. In some instances, such actions can include retrieving andimplementing a rule, retrieving an access-enabling code, generating acommunication (e.g., including an access-enabling code) to betransmitted to another device (e.g., a nearby client-associated device,a remote device, a central server, a web server, etc.), processing areceived communication (e.g., to perform an action in accordance with aninstruction in the communication, to generate a presentation based ondata in the communication, or to generate a response communication thatincludes data requested in the received communication) and so on.

Handheld controller 810 can communicate with a storage controller 820 soas to facilitate local storage and/or retrieval of data. It will beappreciated that handheld controller 810 can further facilitate storageand/or retrieval of data at a remote source via generation ofcommunications including the data (e.g., with a storage instruction)and/or requesting particular data.

Storage controller 820 can be configured to write and/or read data fromone or more data stores, such as an application storage 822 and/or auser storage 824. The one or more data stores can include, for example,a random access memory (RAM), dynamic random access memory (DRAM),read-only memory (ROM), flash-ROM, cache, storage chip, and/or removablememory. Application storage 822 can include various types of applicationdata for each of one or more applications loaded (e.g., downloaded orpre-installed) onto user device 110. For example, application data caninclude application code, settings, profile data, databases, sessiondata, history, cookies and/or cache data. User storage 824 can include,for example, files, documents, images, videos, voice recordings and/oraudio. It will be appreciated that user device 110 can also includeother types of storage and/or stored data, such as code, files and datafor an operating system configured for execution on user device 110.

Handheld controller 810 can also receive and process (e.g., inaccordance with code or instructions generated in correspondence to aparticular application) data from one or more sensors and/or detectionengines. The one or more sensors and/or detection engines can beconfigured to, for example, detect a presence, intensity and/or identifyof (for example) another device (e.g., a nearby device or devicedetectable over a particular type of network, such as a Bluetooth,Bluetooth Low-Energy or Near-Field Communication network); anenvironmental, external stimulus (e.g., temperature, water, light,motion or humidity); an internal stimulus (e.g., temperature); a deviceperformance (e.g., processor or memory usage); and/or a networkconnection (e.g., to indicate whether a particular type of connection isavailable, a network strength and/or a network reliability).

FIG. 8 shows several exemplary sensors and detection engines, includinga peer monitor 830, accelerometer 832, gyroscope 834, light sensor 836and location engine 838. Each sensor and/or detection engine can beconfigured to collect a measurement or make a determination, forexample, at routine intervals or times and/or upon receiving acorresponding request (e.g., from a processor executing an applicationcode).

Peer monitor 830 can monitor communications, networks, radio signals,short-range signals, etc., which can be received by a receiver of userdevice 110) Peer monitor 830 can, for example, detect a short-rangecommunication from another device and/or use a network multicast orbroadcast to request identification of nearby devices. Upon or whiledetecting another device, peer monitor 830 can determine an identifier,device type, associated user, network capabilities, operating systemand/or authorization associated with the device. Peer monitor 530 canmaintain and update a data structure to store a location, identifierand/or characteristic of each of one or more nearby user devices.

Accelerometer 832 can be configured to detect a proper acceleration ofuser device 110. The acceleration may include multiple componentsassociated with various axes and/or a total acceleration. Gyroscope 834can be configured to detect one or more orientations (e.g., viadetection of angular velocity) of user device 110. Gyroscope 834 caninclude, for example, one or more spinning wheels or discs, single- ormulti-axis (e.g., three-axis) MEMS-based gyroscopes.

Light sensor 836 can include, for example, a photosensor, such asphotodiode, active-pixel sensor, LED, photoresistor, or other componentconfigured to detect a presence, intensity and/or type of light. In someinstances, the one or more sensors and detection engines can include amotion detector, which can be configured to detect motion. Such motiondetection can include processing data from one or more light sensors(e.g., and performing a temporal and/or differential analysis).

Location engine 838 can be configured to detect (e.g., estimate) alocation of user device 110. For example, location engine 838 can beconfigured to process signals (e.g., a wireless signal, GPS satellitesignal, cell-tower signal, iBeacon, or base-station signal) received atone or more receivers (e.g., a wireless-signal receiver and/or GPSreceiver) from a source (e.g., a GPS satellite, cellular tower or basestation, or WiFi access point) at a defined or identifiable location. Insome instances, location engine 838 can process signals from multiplesources and can estimate a location of user device 110 using atriangulation technique. In some instances, location engine 838 canprocess a single signal and estimate its location as being the same as alocation of a source of the signal.

User device 110 can include a flash 842 and flash controller 846. Flash842 can include a light source, such as (for example), an LED,electronic flash or high-speed flash. Flash controller 846 can beconfigured to control when flash 842 emits light. In some instances, thedetermination includes identifying an ambient light level (e.g., viadata received from light sensor 836) and determining that flash 842 isto emit light in response to a picture- or movie-initiating input whenthe light level is below a defined threshold (e.g., when a setting is inan auto-flash mode). In some additional or alternative instances, thedetermination includes determining that flash 846 is, or is not, to emitlight in accordance with a flash on/off setting. When it is determinedthat flash 846 is to emit light, flash controller 846 can be configuredto control a timing of the light so as to coincide, for example, with atime (or right before) at which a picture or video is taken.

User device 110 can also include an LED 840 and LED controller 844. LEDcontroller 844 can be configured to control when LED 840 emits light.The light emission may be indicative of an event, such as whether amessage has been received, a request has been processed, an initialaccess time has passed, etc.

Flash controller 846 can control whether flash 846 emits light viacontrolling a circuit so as to complete a circuit between a power sourceand flash 846 when flash 842 is to emit light. In some instances, flashcontroller 846 is wired to a shutter mechanism so as to synchronizelight emission and collection of image or video data.

User device 110 can be configured to transmit and/or receive signalsfrom other devices or systems (e.g., over one or more networks, such asnetwork(s) 170). These signals can include wireless signals, andaccordingly user device 110 can include one or more wireless modules 850configured to appropriately facilitate transmission or receipt ofwireless signals of a particular type. Wireless modules 850 can includea Wi-Fi module 852, Bluetooth module 854, near-field communication (NFC)module 856 and/or cellular module 856. Each module can, for example,generate a signal (e.g., which may include transforming a signalgenerated by another component of user device 110 to conform to aparticular protocol and/or to process a signal (e.g., which may includetransforming a signal received from another device to conform with aprotocol used by another component of user device 110).

Wi-Fi module 854 can be configured to generate and/or process radiosignals with a frequency between 2.4 gigahertz and 5 gigahertz. Wi-Fimodule 854 can include a wireless network interface card that includescircuitry to facilitate communicating using a particular standard (e.g.,physical and/or link layer standard).

Bluetooth module 854 can be configured to generate and/or process radiosignals with a frequency between 2.4 gigahertz and 2.485 gigahertz. Insome instances, bluetooth module 854 can be configured to generateand/or process Bluetooth low-energy (BLE or BTLE) signals with afrequency between 2.4 gigahertz and 2.485 gigahertz.

NFC module 856 can be configured to generate and/or process radiosignals with a frequency of 13.56 megahertz. NFC module 856 can includean inductor and/or can interact with one or more loop antenna.

Cellular module 858 can be configured to generate and/or processcellular signals at ultra-high frequencies (e.g., between 698 and 2690megahertz). For example, cellular module 858 can be configured togenerate uplink signals and/or to process received downlink signals.

The signals generated by wireless modules 850 can be transmitted to oneor more other devices (or broadcast) by one or more antennas 859. Thesignals processed by wireless modules 850 can include those received byone or more antennas 859. One or more antennas 859 can include, forexample, a monopole antenna, helical antenna, intenna, Planar Inverted-FAntenna (PIFA), modified PIFA, and/or one or more loop antennae.

User device 110 can include various input and output components. Anoutput component can be configured to present output. For example, aspeaker 862 can be configured to present an audio output by convertingan electrical signal into an audio signal. An audio engine 864 caneffect particular audio characteristics, such as a volume,event-to-audio-signal mapping and/or whether an audio signal is to beavoided due to a silencing mode (e.g., a vibrate or do-not-disturb modeset at the device).

Further, a display 866 can be configured to present a visual output byconverting an electrical signal into a light signal. Display 866 mayinclude multiple pixels, each of which may be individually controllable,such that an intensity and/or color of each pixel can be independentlycontrolled. Display 866 can include, for example, an LED- or LCD-baseddisplay.

A graphics engine 868 can determine a mapping of electronic image datato pixel variables on a screen of user device 110. It can further adjustlighting, texture and color characteristics in accordance with, forexample, user settings.

In some instances, display 866 is a touchscreen display (e.g., aresistive or capacitive touchscreen) and is thus both an input and anoutput component. A screen controller 870 can be configured to detectwhether, where and/or how (e.g., a force of) a user touched display 866.The determination may be made based on an analysis of capacitive orresistive data.

An input component can be configured to receive input from a user thatcan be translated into data. For example, as illustrated in FIG. 8, userdevice 110 can include a microphone 872 that can capture audio data andtransform the audio signals into electrical signals. An audio capturemodule 874 can determine, for example, when an audio signal is to becollected and/or any filter, equalization, noise gate, compressionand/or clipper that is to be applied to the signal.

User device 110 can further include one or more cameras 876, 880, eachof which can be configured to capture visual data (e.g., at a given timeor across an extended time period) and convert the visual data intoelectrical data (e.g., electronic image or video data). In someinstances, user device 110 includes multiple cameras, at least two ofwhich are directed in different and/or substantially oppositedirections. For example, user device 110 can include a rear-facingcamera 876 and a front-facing camera 880.

A camera capture module 878 can control, for example, when a visualstimulus is to be collected (e.g., by controlling a shutter), a durationfor which a visual stimulus is to be collected (e.g., a time that ashutter is to remain open for a picture taking, which may depend on asetting or ambient light levels; and/or a time that a shutter is toremain open for a video taking, which may depend on inputs), a zoom, afocus setting, and so on. When user device 110 includes multiplecameras, camera capture module 878 may further determine which camera(s)is to collect image data (e.g., based on a setting).

FIG. 9 illustrates sample components of an embodiment of site system180, including connections to NAS 750 and access management system 185.Embodiments of site controller 712 use network manager 920 to connectvia access points 720 (using e.g., WiFi 952, Bluetooth 953, NFC 956,Ethernet 958, and/or other network connections) to other networkcomponents, such as site network 716 and mobile devices 724. In someembodiments, site system 280 uses site controller 712 to control aspectsof a spatial region associated with a resource. An access right grantsaccess to the spatial region during a defined time period. A broadvariety of features can be controlled by different embodiments,including: permanent lights (e.g., with lighting controller 922), lights(e.g., with presentment controller 924), display screens (e.g., withstage display(s) controller 912), permanent display screens (e.g., withpermanent display(s) controller 914), and the sound system (e.g., withthe sound system controller 916).

A more detailed view of NAS 750 is shown, including NAS controller 930coupled to user video storage 932, captured video storage 934,preference storage 936, and 3D model 938. Captured video storage 934 canreceive, store and provide user videos received from mobile devices 724.In some embodiments, site controller 712 triggers the automatic captureof images, audio and video from mobile devices 724, such triggeringbeing synchronized to activities in an event. Images captured by thisand similar embodiments can be stored on both the capturing mobiledevice 724 and user video storage 932. In an embodiment, site controller712 can coordinate the transfer of information from mobile devices toNAS 750 (e.g., captured media) with activities taking place during theevent. When interacting with mobile devices 724, some embodiments ofsite controller 712 can provide end user interfaces 926 to enabledifferent types of interaction. For example, as a part of engagementactivities, site controller may offer quizzes and other content to thedevices. Additionally, with respect to location determinations discussedherein, site controller can supplement determined estimates withvoluntarily provided information using end user interfaces 926, storedin a storage that is not shown.

In some embodiments, to guide the performance of different activities,site controller 712 and/or other components may use executable code 938tangibly stored in code storage 939. In some embodiments, siteinformation storage 937 can provide information about the site, e.g., 3Dmodels of site features and structure.

Referring next to FIG. 10A, an example of a communication exchange 1000a involving primary load management system 1014 and each of a pluralityof secondary load management systems 1016 a, 1016 b is shown. In someinstances, secondary load management system 1016 a is managed by anentity different than an entity that manages secondary load managementsystem 1016 b. Primary load management system 1014 may include and/orshare properties with a primary assignment management system 214. Eachof one or both of secondary load management system 1016 a and 1016 b mayinclude or correspond to a secondary assignment system 216.Communications shown in FIG. 10 may be transmitted over one or morenetworks, such as network 270, the Internet and/or a short-rangenetwork.

In one instance, one of secondary load management system 1016 a or 1016b is managed by a same entity as manages primary load management system1014. In one instance, each of secondary load management system 1016 and1016 b is managed by an entity different than an entity managing primaryload management system 1014. Primary load management system 1014 caninclude a system that, for example, manages a master access-rightassignment data store, distributes access codes, performs verificationdata for access attempts, and so on. Secondary load management systems1016 a, 1016 b can include systems that, for example, facilitateassignment of access codes to users. For example, secondary loadmanagement systems 1016 a, 1016 b can be configured to requestallocation of access-right slots, which may result in a temporary orfinal allocation or assignment to the system, a hold on the access-rightslots, and/or a distribution of data pertaining to the slot(s).Secondary load management systems 1016 a, 1016 b may then facilitatetransmission of the access-right slots to one or more users and identifya user that has requested one or more particular access-right slots. Thesecondary load management system can then facilitate an assignment ofthe access-right slots by (for example) transmitting one or more accesscodes to the user device, identifying the user to primary loadmanagement system 1014 or updating assignment data.

Communication exchange 1000 a begins with transmission of one or morerule specifications from each secondary load management system 1016 a,1016 b to primary load management system 1014. The rule specificationcan include one or more request parameters identify parameters of a loadrequested for allocation. For example, a rule specification can includea specification pertaining to a size of a target load (e.g.,corresponding to a number of access-right slots). The specification mayinclude a particular number or a threshold. A rule specification caninclude a specification of a type of at least part of the load, such asone that identifies a resource or type of resource and/or one thatidentifies a characteristic of one or more access-right slots (e.g., alocation). The specification may include a first allocation parameterthat may identify a value for which access-right slots are beingrequested.

In some instances, a rule and/or request corresponds to a singleresource, while in others, the rule and/or request corresponds tomultiple resources. For example, a request may be for access-rightresults pertaining to each of three resources or to each resourceavailable at a location in a season. Thus, in some instances, a rulespecification identifies or is indicative of a number of resources.Resources may, but need not, be specifically identified in a rulespecification, rule and/or request. For example, a rule specificationmay indicate that a defined number or range (e.g., 100-200) ofaccess-right slots is requested for any given resource within a definedtime period (e.g., year).

A rule specification can include an allocation parameter that identifiesa parameter for allocating a load should it be allocated to thesecondary load management system. To illustrate, secondary loadmanagement system 1016 a, 1016 b may be configured to receiveallocations of access-right slots but to attempt to facilitateassignment of the access-right slots to users. Communication exchange1000 a can be configured so as to promote facilitated distribution tousers upon allocation of access-right slots to a secondary loadmanagement system. Early provision of allocation parameters by asecondary load management system can promote such quick facilitateddistribution.

For example, an allocation parameter can identify one or morecommunication channels (e.g., webpages, portals,information-distribution protocols, email addresses, etc.) fortransmitting information pertaining to at least part of the load to eachof one or more devices and/or an a second allocation parameter. Thisinformation may enable primary load management system 1014 to (forexample) automatically provide information pertaining to allocatedaccess-right slots via the communication channel(s) and/or to verifythat allocation parameters comply with one or more primary-system rules(e.g., that may include an upper and/or lower threshold for anallocation parameter and/or limits on which communication channels maybe used).

Primary load management system 1014 can define a rule for each secondaryload management system 1016 a, 1016 b based on the rule specifications.The rules can be stored in a secondary system rules data store 1018.

Primary load management system 1014 can further include a load datastore 1020. Load data store 1020 can include, for example, informationpertaining to which access-right slots for a given resource areavailable and information pertaining to each of those slots. Load datastore 1020 can further identify information pertaining to one or moredefined loads, such as which access-right slots are corresponding to theload, to which secondary load management system a load has beenallocated, whether an allocation includes any restrictions (e.g., timelimits).

Primary load management system 1014 can assess whether a set ofavailable access-right slots corresponds to request parametersidentified in any secondary-system rules. For example, it can bedetermined whether a resource type corresponds to that specified in arequest parameter, whether a quantity (and/or contiguous quantity)corresponds to that specified in a request parameter, whether a type ofthe access-right slots corresponds to that specified in a requestparameter, and/or whether the quantity of access-right slots can beallocated for a value that corresponds to a first allocation parameterspecified in a request parameter (e.g., the determination being based ondefined values or thresholds associated with the access-right slotsand/or a primary-system rule).

In some instances, it may be determined that request parametersidentified in rules for multiple secondary load management systemcorrespond to a same load or to a same at least part of a load. Primaryload management system 1014 may include a switch, such as a contentswitch, that may evaluate a load, rules and/or systems to determine towhich secondary load management system 1016 a load is to be allocated oridentified. In these instances, the rules and/or systems may beprioritized to determine to which entity the load is to be allocated.The prioritization may depend on, for example, defined prioritizationsof the systems, a time at which rule specifications were submitted(e.g., prioritizing early submission), a size parameter (e.g.,prioritizing either lower or larger size requests), and/or firstallocation parameters (e.g., prioritizing larger first allocationparameters).

It will be appreciated that, in various instances, a load may begenerated in response to evaluation of a load (e.g., in an attempt todefine a load that accords with request parameters), or a load may befirst defined (e.g., based on which access-right slots remain availableand/or distribution priorities of the primary load management system)and it is then determined which rule to which the load corresponds. Insome instances, a primary-system rule as to which access-right slots areto be included in a load and/or a secondary-system rule as to whichaccess-right slots are requested may depend on information, such as anenvironmental characterization corresponding to a resource, a throughputmonitor and/or a discrepancy associated with a resource (e.g., a spreador line associated with a resource). In some instances, a primary-systemrule and/or secondary-system rule may include a function that relates anenvironmental characteristic, throughput characteristic and/ordiscrepancy with an allocation parameter (e.g., such that largerdiscrepancies, poorer environmental characteristics and/or lowerthroughput prospects result in lower allocation parameters).

When it is determined that a load corresponds to a secondary-system rule(and/or any prioritization is performed), primary load management systemcan transmit a trigger indication to the associated secondary loadmanagement system 1016 a. The trigger indication may identifycharacteristics of the load (e.g., a size, type of one or moreaccess-right slots, resource, and/or allocation value). In someinstances, the trigger indication may identify a rule and/or whatspecifications were defined in the triggered rule.

In some instances, communication exchange 1000 a is configured so as toprovide a secondary load management system 1016 a a defined time periodfor transmitting a request responsive to a trigger indication.Access-right slots may, but need not, be placed on hold for the timeperiod. Should a request not be received within the time period, primaryload management system 1014 may transmit a same or different triggerindication to another secondary load management system with a rulecorresponding to the load or may redefine a load so as to correspondwith a rule of another secondary load management system and transmit atrigger indication accordingly. In some instances, a trigger indicationis simultaneously transmitted to multiple secondary load managementsystems 1016, and a load may be allocated to a system that thereafterrequests the load (e.g., in accordance with a first-responder or othersecondary-system selection technique).

Secondary load management system 1016 a can then transmit a requestcommunication back to primary load management system that requests theload. Primary load management system 1014 can then transmit a responsecommunication that confirms that the load is being allocated. In someinstances, the response communication is transmitted subsequent to or intemporal proximity of a time at which a charge is issued or collectedfor the load. In some instances, then response communication includesfurther information about the load. For example, location ofaccess-right slots in the load may be more precisely identified.

Secondary load management system 1016 a can store data pertaining to theload in a load data store 1022. Load data store 1022 may further trackstatuses of access-right slots so as to be able to identify whichaccess-right slots have been assigned to users. Secondary loadmanagement system 1016 a can further manage and/or have access to aresource specification data store 1024 that can associate identifiers ofvarious resources with corresponding information. The resourcespecifications may be, for example, included in a trigger-information orresponse communication from primary load management system 1014;identified via an external search (e.g., web crawl), and so on. Resourcespecifications may include, for example, a location and/or a date andtime.

A user device 1026 can also transmit rule specifications to one or moreof primary load management system 1014 and 1016 a. The rulespecifications may include request parameters, such as a sizespecification, type specification and/or assignment value (e.g., thatmay be precisely identified or a threshold). When rule specificationsare transmitted and/or availed to secondary load management system 1016a, a corresponding user rule can be defined for the user device and/oruser.

Secondary load management system 1016 a can distribute data of aresource (or multiple resources) corresponding to the load allocated tothe system. The resource data can include one or more resourcespecifications stored at resource specification data store 1024. Theresource data may further include data associated with one or moreaccess-right slots included in the load. For example, the resource datamay identify a time and location of a resource and a location of each ofone or more access-right slots. In some instances, the resource datafurther includes an allocation parameter, such as the second allocationparameter and/or one defined based thereupon included in asecondary-system rule specification or included in a rule associatedwith secondary load management system 1016 a.

In some instances, secondary load management system 1016 a controls thetransmission of the resource data to one or more user devices 1026. Insome instances, primary load management system 1014 facilitates thetransmission. For example, the data may be identified in an interfaceprovided, controlled and/or managed by secondary load management system1016 a, but primary load management system 1016 may have authorizationto update the webpage, and thus primary load management system canupdate the secondary-system to include the resource data.

In some instances, resource data is selectively transmitted to userdevices. For example, resource data may be transmitted only to the userdevices associated with user rules corresponding with at least part ofthe load.

User device 1026 can request assignment of at least part of the load.The user request can identify, for example, one or more access-rightslots (e.g., and/or one or more resources). Secondary load managementsystem 1016 a can evaluate the request and respond with load responsedata. Such a response may be conditioned (for example) on confirmingcompletion of the assignment process. The load response data may (forexample) indicate that the assignment has been accepted and/or includeconfirmation data. Upon such acceptance, secondary load managementsystem 1016 a can also transmit assignment data to primary loadmanagement system. The load data can include an identification of theuser device (or corresponding information, such as a name, email,profile, device identifier or phone number of a corresponding user)and/or one or more access-right slots being assigned. Primary assignmentmanagement system can update an assignment data store and/or load datastore 1020 to reflect the assignment.

Primary load management system 1014 can then retrieve access code datafrom an access code data store 1030 and transmit the access code data touser device 1026. The access code data can correspond to the one or moreaccess rights being assigned to the user. The access code data can betransmitted (for example) immediately, at a defined time (e.g., relativeto a time of a resource), or upon receiving a request (e.g., triggeredby a user input or detecting that a user device has crossed a geofencecorresponding to a resource).

User device 1026 can store the access code(s) in an access-code datastore 1030 b. Subsequently, user device 1026 can retrieve theaccess-code data and transmitting it to a site controller 712 (e.g.,upon detecting the site controller, upon receiving a request from thesite controller or in response to detecting a corresponding user input).Site controller 712 can include one located at a resource location. Sitecontroller 712 can transmit the access-code data to primary loadmanagement system 1014, which can then determine whether the code is avalid code, has not been previously redeemed and/or corresponds to oneor more characteristics (e.g., a resource associated with or identifiedby the site controller, a time, a device characteristic, etc.). A resultof such determination(s) can be transmitted back to site controller 712such that a user can then be granted or denied requested access to aresource.

It will be appreciated that one, more or all communications representedin communication exchange 1000 a can be transmitted via (for example) aweb site, a web portal, another portal, an email exchange, a message(e.g., SMS message) exchange, and/or an API.

It will be appreciated that part or all of a communication exchange canbe performed in an automated or semi-automated manner. For example, oneor more rules (e.g., secondary-system rules or user rules) can bedefined so as to trigger automatic allocation or assignment upondetecting data that corresponds to request parameters in the rules. Asanother example, the one or more rules can be defined so as to trigger anotification communication to the user device or secondary loadmanagement system that includes an alert that the request parameters aresatisfied and enable to user device or secondary load management systemto transmit a request for allocation or assignment.

It will also be appreciated that various modifications to communicationexchange 1000 a are contemplated. For example, in one instance,secondary load management system 1016 a may at least partly manageaccess codes. For example, one or more access codes corresponding to aload may be transmitted from primary load management system 1014 tosecondary load management system 1016 a as part of a response. Secondaryload management system 1016 a may then transmit select access codes to auser device 1026, and (in various instances) either primary loadmanagement system 1014 or secondary load management system 1016 a mayprovide verification of the code to site controller 712.

Referring next to FIG. 10B, another example of a communication exchange1000 b involving primary load management system 1014 and each of aplurality of secondary load management systems 1016 a, 1016 b is shown.In this instance, two different types of access code data are associatedwith an assignment.

As shown, in response to an initial assignment of an access-right slot,primary load management system 1014 transmits first access code data touser device 1026. The first access code data may include datarepresenting that access to a resource has been authorized. However, inthis instance, the first access code data may lack a precision ofassociation that would associate the first access code data with one ormore particular access characteristics. For example, the data may lackinformation that would identify a particular location within a resourcearea for which access is to be granted.

Subsequently (e.g., after a predefined time period, such as within adefined period from a resource time; and/or when a user device 1026crosses a geofence corresponding to a resource, and/or when a userdevice 1026 receives input or a site-controller request indicating thataccess data is to be transmitted to a nearby site controller), userdevice 1026 may retrieve the first access code data and transmit it(e.g., via a short-range communication) to a first site controller 712a.

First site controller 712 a may communicate with primary load managementsystem 1014 to verify the data, in a manner similar to that describedherein. Upon detecting that the first access code data has beenverified, first site controller 712 a can transmit second access codedata to user device 1026. The second access code data have a precisionof association that associates the data with one or more particularaccess characteristics. The second access code data may be, for example,generated at first site controller 712 a or received from primary loadmanagement system (e.g., as part of the verification communication or aspart of another communication). The particular access characteristicsmay be identified based on, for example, a technique described in U.S.application Ser. No. 14/063,929, filed on Oct. 25, 2013, which is herebyincorporated by reference in its entirety for all purposes. Theparticular access characteristics may be identified based on, forexample, for which and/or how many access-right results first accesscode data had been previously verified and/or which and/or how manysecond access codes had been generated and/or transmitted.

The second access code data may indicate where access to a resource isauthorized, and user device 1026 may thus move to a correspondinglocation. In some instance, a second site controller 712 b is associatedwith the corresponding location. User device 1026 may then transmit thesecond access code data (e.g., when user device 1026 detects that it hascrossed a geofence corresponding to the location and/or when user device1026 receives input or a site-controller request indicating that accessdata is to be transmitted to a nearby site controller) to second sitecontroller 712 b. Second site controller 712 b can determine whether thecode is verified (e.g., valid, has not been previously used, and/orcorresponds to the user device 1026 and/or location). The determinationcan include (for example) transmitting the second access code data toanother device (e.g., primary load management system 1014, a localserver, or another site controller, such as first site controller 712 a)and receiving second verification data that indicates whether the secondaccess code data is verified. The determination can, alternatively oradditionally, include a local determination, which may be based (forexample) on comparing the second access code data to data in a localaccess-code data store to determine whether there is a match and/orwhether the second access code data (or corresponding access code datathat is associated with same one or more particular characteristics) hasbeen previously verified. The local access-code data store may bepopulated by second site controller 712 b, for example, in response tocommunications from one or more other site controllers and/or primaryload management system 1014 that identify second access code data thathave been issued.

FIG. 11 is a block diagram illustrating a network environment forenabling access rights to be queried in a hierarchical manner based onresource-affinity parameters. FIG. 11 illustrates network environment1100, which includes primary load management system 1014, web server1110, messaging system 1115 (e.g., an SMS provider), and mobile device1120. Primary load management system 1014 may be configured tocommunicate with web server 1110 and messaging system 1115 throughnetwork 1105. Network 1105 may be any public and/or private networkconnected to the Internet.

Web server 1110 may include one or more servers configured to host oneor more webpages associated with the primary load management system1014. For example, web server 1110 may host an access-right assignmentwebpage, which facilitates assigning access rights to users. Further,web server 1110 may also facilitate the assignment process forrequesting assignment of one or more access rights that are publiclyavailable to be queried by user devices.

Messaging system 1115 can include one or more servers that facilitatecommunications between primary load management system 1014 and mobiledevices. For example, messaging system 1115 can implement a messagingservice, such as SMS or push notifications, to communicate with mobiledevices (e.g., smartphones).

Mobile device 1120 can be any end user device that is configured to beoperated by a user. Examples of mobile device 1120 can includesmartphones, tablet devices, laptops, or any mobile computing device. Itwill be appreciated that non-portable devices may also be included innetwork environment 1100, and as such, while mobile device 1120 isportable, the present disclosure is not limited thereto. Mobile device1120 may be operated by a user. The user may operate mobile device 1120to access the one or more webpages hosted by web server 1110 in order toquery for and/or request assignment of access rights to a resource.

However, using a webpage to query for available (e.g., unassigned)access rights for the purpose of assignment to a user device may be slowand inefficient during times of high processing load (e.g., a largenumber of user devices are querying databases for available accessrights). Accordingly, in some implementations, mobile device 1120 may beregistered with primary load management system 1014 in order to avoidhaving to request assignment of access rights using the webpagesdescribed above. In these implementations, the user may define a profilewith primary load management system 1014, and the profile can includeone or more characteristics of the user or settings defined by the user.For example, the profile can include a phone number that can be used tocommunicate with mobile device 1120. According to example embodiments ofthe present disclosure, the user operating mobile device 1120 can avoidthe challenges of requesting access rights using the webpage duringtimes of high request loads. For instance, when an available accessright that satisfies predetermined conditions (defined by the user inthe profile), then the access right may be automatically and/ortentatively assigned to the user. When the access right is released(e.g., available for assignment), the primary load management system1014 may transmit one or more signals to messaging system 1115. The oneor more signals may include instructions that cause the messaging system1115 to transmit a message to mobile device 1120 using a messagingservice (e.g., SMS). In some implementations, the message may include anotification that one or more access rights have been automaticallyand/or tentatively assigned to the user. The user may transmit a messageback to the primary load management system 1014 using the messagingsystem 1115 (e.g., by responding via text message). For example, theuser may respond with a keyword (e.g., “YES”) to indicate that the userseeks to proceed with requesting assignment of the access right. If theuser does not want to complete the request for assignment of theautomatically and/or tentatively assigned access right, the user caneither not respond or respond with a predefined keyword, such as “NO”(e.g., in which case the reservation of the access right will expire andthe access right will be automatically and/or tentatively assigned tothe user with the next highest resource-affinity parameter). The usermay have a predefined amount of time to respond (e.g., 5, 10, 15minutes). When the user transmits the message indicating that the userwould like to request assignment of the access right (e.g., bytransmitted a message with the text “YES”), the primary load managementsystem 1014 can automatically assign the access right on behalf of theuser.

It will be appreciated that the message can also include a notificationthat the access right is available without reserving the access rightfor the user. In this case, the user can log into the access-rightassignment system associated with primary load management system inorder to request assignment of the access right.

FIG. 12 is a swimlane diagram illustrating an example data flow 1200 ofthe network environment of FIG. 11. Data flow 1200 can include one ormore communications between the primary load management system, the webserver, the messaging system, and the mobile device (for example, asillustrated in FIG. 11). Data flow 1200 begins at block 1205 where theprimary load management system generates unique access codes(representing unique access rights to a resource). At block 1210, theaccess rights that correspond to the generated access codes arequeriable though an interface that can facilitate access to the webserver. When the access rights are available or enabled to be queried byuser devices, they become searchable using the interface (e.g., at block1215). Further, when the access rights are available or enabled to bequeried by user devices, the access rights are also available to beassigned to user devices requesting assignment of the access rights. Forexample, a particular user device can query for access rights thatsatisfy a certain constraint (e.g., a location of the access right orresource), and then the user device can request that the access right(s)that result from the query be assigned to the user device. The userdevice may have to complete an assignment process to have the accessright(s) assigned to the user device. However, when access rights areaccessible for querying, the databases that store the access rightsoften experience durations of high load around the time when the accessrights are initially available to be queried. Example embodimentsdescribed in the present disclosure (e.g., in blocks 1220-1260) areprovided to address the technical problem of databases overloaded withuser requests.

At block 1220, access rights that are not yet enabled to be queried maybe identified. For example, in certain cases, a subset of a set ofaccess rights may be initially assigned to an entity associated with theresource before the set of access rights are available to be queried byuser devices. If one or more access rights included in the subset ofaccess rights are not re-assigned from the entity to another user devicebefore a particular time period associated with the resource, the one ormore access rights that were not re-assigned may be enabled to bequeried by user devices (e.g., the general public). However, in certainembodiments, instead of enabling the one or more access rights of thesubset of access rights to be queried by user devices, the primary loadmanagement system may automatically assign the one or more access rightsto certain user devices that satisfy a predefined objective (e.g., userdevices associated with users who are predicted as being likely toultimately access the resource during a defined time period).

At block 1225, the primary load management can access theresource-affinity parameter for each user device that has previouslyregistered with the primary load management system. Theresource-affinity parameter may be stored in a data store associatedwith the primary load management system. At block 1230, the primary loadmanagement system may identify the user with the highestresource-affinity parameter (e.g., the user whose resource-affinityparameter indicates the greatest likelihood of meeting an objective ascompared to other the resource-affinity parameters of users), fromamongst all resource-affinity parameters of various users, andautomatically and tentatively assign the one or more access rights tothat user. In some examples, automatically and/or tentatively assigningan access right may be implemented by storing a hold instruction inassociation with the one or more access rights for a predefined periodof time (e.g., 5, 10, 15 minutes). Storing a hold instruction inassociation with the one or more access rights indicates to the primaryload management system that the access right is (at least temporarily)no longer queriable by user devices or searchable through the interfacefor the predefined period of time. Further, the hold instruction allowsthe user to determine whether or not he or she would like to be assignedto the one or more access rights. The hold instruction also provides theuser with the time to complete the assignment process. The holdinstruction causes the primary load management system to automaticallyprovide the user with the chance to request assignment of the one ormore access rights before the one or more access rights are accessiblefor querying by other user devices (e.g., the public).

At block 1235, the primary load management system can transmit anotification signal to the user device with the highestresource-affinity parameter (or the user device associated with theresource-affinity parameter that indicates the greatest likelihood ofmeeting an objective). The notification signal can cause the user deviceto be notified that an access right has been automatically and/ortentatively assigned (e.g., temporarily reserved) to the user device.For example, transmitting the notification signal can include generatingan instruction that is transmitted to the messaging system. When theinstruction is received at the messaging system, the instruction cancause the messaging system to generate and transmit a text message tothe mobile device associated with the user. The text message can includea message indicating that an access right has been automatically and/ortentatively assigned to the user device (and is not available to bequeried by other user devices), and that the user can request assignmentof the access right by responding with a keyword (e.g., “YES”). In someexamples, the text message can also include a disclaimer that thetentatively assigned access right is only temporarily assigned for apredefined time period (e.g., 5, 10, 15 minutes), and that after thattime period, the access right will no longer be assigned to the user. Atblock 1240, the messaging system can receive the instruction andgenerate a text message for the mobile device. At block 1245, the mobiledevice can receive the text message and the text message can bedisplayed on the mobile device. It will be appreciated that the messagemay be transmitted to the mobile device and presented on a nativeapplication that is running on the mobile device. For example, themessage can be a push notification that is presented on the mobiledevice using the native application. It will be appreciated that themessage can include any text, and thus, the present disclosure is notlimited to the message content described above.

At block 1250, if the user decides to proceed with requesting assignmentof the one or more access rights, the mobile device can receive inputcorresponding to the user's decision. As only a non-limiting example,the user can type in “YES” into the text message application running onthe mobile device and send the message in response to the notificationreceived at block 1245. Alternatively, if the user decides not torequest assignment of the access right, the user can ignore the messageor respond in the negative (e.g., respond with a text message of “NO”).In these examples, the user has a predetermined period of time (e.g., 5,10, 15 minutes, etc.) to decide and respond for the access rights. Theinitial message received at block 1245 may indicate that the reservationof the access right will expire after a predetermined time period. Atblock 1255, the message transmitted by the mobile device (in the case ofthe user accepting to request assignment of the access rights) may bereceived at the messaging system and relayed to the primary loadmanagement system. It will be appreciated that the messaging system canreceive the text message response from the mobile device, transform thetest message into one or more signals that can be transmitted over thenetwork (e.g., network 105), and then relay the one or more signals tothe primary load management system.

At block 1260, the primary load management system receives theinstruction to assign the access right. The primary load managementsystem can then access the user's profile to obtain the data needed tocomplete the assignment process. The option to assign access rights inthe manner described in process 1200 may only be available to users whohave completed their profiles. It will be appreciated that the steps oftransmitting a notification and receiving an instruction (e.g., blocks1235-1250) may be removed from process 1200. In some examples, one ormore access rights may be automatically assigned to users based on theusers' resource-affinity parameters. For instance, an access right maybe assigned to the user associated with the resource-affinity parameterthat indicates the greatest likelihood of meeting an objective ascompared to other users. The primary load management system mayiteratively assign access rights (e.g., without requiring that the userdevice transmit instructions to assign the access rights to the primaryload management system) to the users by assigning access rights to userswith the greatest likelihood of meeting an objective, and iteratively,assign access rights to users with the next greatest likelihood ofmeeting the objective. It will be appreciated that the primary loadmanagement system may select access rights to automatically assign tousers by accessing the profile associated with a user to identify one ormore constraints for querying access rights (e.g., a location of anaccess right or resource preferred by the user and indicated in theuser's profile).

FIG. 13 is a block diagram illustrating network environment 1300 forgenerating contextualized resource-affinity parameters for users.Network environment 1300 can include global resource-affinity parameterdata store 1305 and local resource-affinity parameter data store 1315.Global resource-affinity parameter data store 1305 can store datastructure 1310, which includes the global resource-affinity parametersfor one or more users (e.g., User A, User B, User C, and so on). Localresource-affinity parameter data store 1315 can store data structure1320, which includes the local resource-affinity parameter for one ormore users (e.g., User A, User B, User C, and so on). Each of the globalresource-affinity parameters and local resource-affinity parameters canbe generated by accessing and processing a plurality of data points,described herein. Further, in some examples, each of a globalresource-affinity parameter and a local resource-affinity parameter maybe generated for a particular user. In some examples, either a global orlocal resource-affinity parameter can be generated for a particularuser.

Further, the global resource-affinity parameter data points and thelocal resource-affinity parameter data points can each be fed into amachine-learning model to generate a result that indicates a likelihoodof the user accessing a resource (e.g., the likelihood being representedby the contextualized resource-affinity parameter). The engine 1320 canimplement the machine-learning techniques to compute the contextualresource-affinity parameter for a user. For example, the combination ofthe global resource-affinity parameter and the local resource-affinityparameter may be implemented using one or more ensemble method learningalgorithms. In some implementations, the algorithm used to calculateglobal resource-affinity parameters may be a classifier model (e.g., asupport vector machine (SVM) model, kernel methods, etc.), however, thepresent disclosure is not limited thereto. In some implementations, thealgorithm used to calculate local resource-affinity parameters may be arandom forest model, however, the present disclosure is not limitedthereto. The algorithms executed to calculate the global and localresource-affinity parameters may be the same or may be different fromeach other. In some implementations, the contextualizedresource-affinity parameter may be a combination of the calculatedglobal resource-affinity parameter and the calculated localresource-affinity parameter. Combining the global resource-affinityparameter and the calculated local resource-affinity parameter mayinclude any combination technique, including averaging, summing,subtracting, multiplying, dividing, a weighted combination, or anycomplex combination technique.

While FIG. 13 illustrates that resource-affinity parameters for User A,User B, and User C are stored in each of data structures 1310 and 1320,it will be appreciated that any number of users can be represented ineach of the data structures. For the purpose of illustration, User C isused to explain the global and local resource-affinity parameters.

As a non-limiting example, the global resource-affinity parameter canrepresent the likelihood that a user will ultimately access any resourcegenerally. The global resource-affinity parameter is not specific to aparticular resource, but rather the global resource-affinity parameterrepresents the general likelihood the user will access any resource. Insome cases, the global resource-affinity parameter can represent thedegree to which the user is predicted to be a bot. In some cases, theglobal resource-affinity parameter can represent the likelihood that auser will transfer an access right to another user.

Non-limiting examples of data points that are used to calculate theglobal resource-affinity parameter can include a distance between adetected user location and any resource-associated locations (e.g.,spatial regions of a resource), previous access right assignment data(e.g., has the user transferred other access rights previously?), thenumber of access rights that were assigned to the user within aspecified time period, frequency of being assigned to access rights thatenable access to a resource during a time period, and being assigned toaccess rights that enable access to another resource during that sametime period, has the user requested assignment of multiple sets ofaccess rights in different transactions, third-party data sets, thelocal resource-affinity parameter of the user (e.g., the localresource-affinity parameter can be used as a data point for the globalresource-affinity parameter, and vice versa), whether or not the userhas requested assignment of an access right to a resource associatedwith a location that is different from the detected location of the userdevice (e.g., the location associated with the detected IP address),whether or not (and how many times) an access right requested by theuser has been detected on a secondary load management system, how manytimes the user has ultimately accessed any resources using valid accessrights, and other suitable data points. As described above, the globalresource-affinity parameter indicates a likelihood of meeting anobjective, however, the objective is not specific to a particularresource, but rather, indicates the likelihood of meeting an objectiveassociated with resources generally.

Continuing with the non-limiting example above, the localresource-affinity parameter may be specific to an access right to aresource. For example, the local resource-affinity parameter canrepresent a likelihood that a user will ultimately access a particularresource during a time period when the resource is enabled to beaccessible.

Non-limiting examples of data points that are used to calculate thelocal resource-affinity parameter can include any one or more of thedata points used for the global resource-affinity parameter, andadditionally or alternatively, affinity data from social media networks,historical data representing which web servers were previously accessed,the data provided by the user during an initialization process, devicetype used during the initialization process (e.g. to register the user),whether or not the user has previously accessed resources associatedwith a particular entity, whether or not the user has accessed thespecific resource before, whether or not the user has previouslytransferred an access right to the particular resource to another userdevice, whether or not the user requested assignment of an access rightto a resource associated with a location that is different from thedetected user location (e.g., the location associated with the detectedIP address), and other suitable data points. It will be appreciated thatthere may be overlap between the global resource-affinity parameter datapoints and the local resource-affinity parameter data points. Asdescribed above, the difference between the global resource-affinityparameter and the local resource-affinity parameter is that the globalresource-affinity parameter represents a likelihood of the user meetingan objective associated with resources generally, whereas, the localresource-affinity parameter represents a likelihood of the user meetingan objective associated with a particular resource. It will beappreciated that the data points associated with globalresource-affinity parameter may be inputted into the samemachine-learning model or a different machine-learning model as the datapoints associated with the global resource-affinity parameter.

It will be appreciated that the global resource-affinity parameter andthe local resource-affinity parameter can be any integer or non-integerbetween any range of values. Further, the range of values the globalresource-affinity parameter may or may not be the same as the range ofvalues for the local resource-affinity parameter. In someimplementations, the range of values for each of the globalresource-affinity parameter and the local resource-affinity parametermay any value between zero and one. In some implementations, the globaland local resource-affinity parameters can be used to label users eitherpositively or negatively. As a non-limiting example, when a user devicecompletes the assignment process for an access right (e.g., the userrequests that the access right be assigned to the user, and the accessright is ultimately assigned to the user), and that user ultimatelyaccesses the resource during the time period when the resource isaccessible, the user can be labeled positively. In this example, aglobal resource-affinity parameter of 0.9 may be calculated for theuser, which indicates a high likelihood of meeting an objectiveassociated with resources generally. As another example, if the userdevice completed the assignment process, and the access right wasdetected at a secondary load management system, the user may be labelednegatively. In this example, a global resource-affinity parameter of 0.3may be calculated for the user, which indicates a low likelihood ofmeeting an objective associated with resources generally.

Advantageously, if User C is requesting assignment for Resource A, butUser C commonly transfers access rights to other user devices, thecontextual resource-affinity parameter for User C in the context ofResource A may indicate that User C is likely to access Resource Aduring the time period when Resource A is accessible, whereas, thecontextual resource-affinity parameter for User C in the context ofResource B may indicate that User C is not likely to access Resource Bduring the time period when Resource B is accessible.

FIG. 14 is a block diagram illustrating network environment 1400 forthrottling access-right assignment workflows based on current systemload(s). In some implementations, network environment 1400 may includebot 1405, server 1410, computer 1415, and mobile device 1420. Networkenvironment 1400 may also include access management system 1480, whichmay be a system that manages the assignment of access rights to varioususers. For example, access management system 1480 can store uniqueidentifiers that uniquely identify access rights. Access managementsystem 1480 may also store (in association with each unique identifier)a user identifier associated with a user to which the access right(s) isassigned. Bot 1405 may include scripts that can be executed toautonomously perform one or more functions (e.g., accessing an inventoryof access rights). Bot 1405 can use Application Programming Interfaces(APIs) to interact with systems. Server 1410 may include one or moreservers configured to directly interact with access management system1480 (e.g., using scripts). For example, server 1410 may automaticallytransmit a communication to access management system 1480 to query foraccess rights to a resource without a human user initiating theinteraction. In some cases, server 1410 can execute bot 1405. Computer1415 can be operated by a user to interact with access management system1480 to request assignment to access rights to resources. Mobile device1420 can also be operated by a user to interact with access managementsystem 1480 to request assignment of access rights to resources.

Each of bot 1405, server 1410, computer 1415, and mobile device 1420 mayindividually transmit a communication (each at any time) to assignmentmanagement system 1480. For example, a communication from mobile device1420 may correspond to a request to access a database storing aplurality of access rights to a resource. Detection layers 1425, 1430,and 1435 can detect and/or control unauthorized access to databasesassociated with access management system 1480. It will be appreciatedthat any number of detection layers may be implemented, and the variousdetection layers may be the same or different from each other. Forexample, detection layers 1425, 1430, and 1435 may each include adetection system or service that detects the presence of bots, hackers,specific systems (e.g., secondary management systems), or unauthorizeduser access using any number of detection techniques (e.g., IP blocking,client time limits, client request frequency limits, client requestlimits on access inventory, reverse TURING tests, speed or frequency ofqueries during a time period, API access behavior pattern evaluation,bot pattern evaluation of sensor data associated with the devicetransmitting the communication, and other suitable techniques), and thenblocks the detected communications, systems, or users. As illustrated inFIG. 14, detection layers 1425, 1430, and 1435 detect thatcommunications from bot 1405, server 1410, and computer 1415 are to beblocked because these communications were detected as originating by anunauthorized bot, server, or hacker, for example.

However, as illustrated in FIG. 14, the communication from mobile device1420 may be communicated to access management system 1480 because themobile device was not detected by detection layers 1425, 1430, and 1435,and thus, is likely to originate from an authorized human user. Forexample, the communication transmitted from mobile device 1420 maycorrespond to a request to access one or more databases that stores aplurality of access rights to resource(s). The user operating mobiledevice 1420 may be requesting access to the database of access rights inorder to request that one or more of those access rights be assigned tomobile device 1420, which enables the user to gain access to theresource. Upon receiving the communication from mobile device 1420,access management system 1480 can process the communication using firstqueue management system 1440.

In some implementations, first queue management system 1440 may includeone or more processors on which executable code (e.g., instructions) isstored, a queue, and/or a memory. For example, first queue managementqueue 1440 may execute a first workflow that enables mobile device 1420to query one or more databases that store access rights to resources.The first workflow may include one or more steps, including but notlimited to, prompting mobile device 1420 for login credentials,accessing user parameters database 1445 to evaluate one or more datapoints using a machine-learning model to generate a resource-affinityparameter, accessing load detector 1450 to determine a current load ofcommunications received at primary load management system 1455 and/orsecondary load management system 1460, and generating a first throttlefactor to control the first workflow. Further, the secondary loadmanagement system 1460 may not generate the unique access codes, butrather, may provide a platform that enables users to reassign accessrights to other users (e.g., the users who are reassigning the accessrights may not ultimately access the access right during the time periodwhen the access right is accessible, but instead, the user who receivesthe reassigned access right is the one who may ultimately access theresource during the time period). The current load may be based on anumber of requests received at either or both of the primary loadmanagement system 1455 and the secondary load management system 1460.While the secondary load management system 1460 is illustrated in FIG.14 as being within the access management system 1480, it will beappreciated that the secondary load management system 1460 may also bein a network that is outside or external to the access management system1480. A current load may include a time or time period at orsubstantially near the time the communication is received. In someimplementations, the first throttle factor generated by the first queuemanagement system 1440 may be used to control the speed or frequency atwhich the steps of the first workflow are provided to mobile device1420. For example, a first throttle factor may be a value, score,parameter, attribute, grade, or other suitable indicator that representshow fast or slow the steps are to be provided to mobile device 1420. Asa non-limiting example, if the first throttle factor is generatedbetween 0 and 1, such values approaching 0 represent steps of the firstworkflow being provided slower, whereas, values approaching 1 representsteps of the first workflow being provided faster (e.g., the scale of 0to 1 being a scale of slow to fast). First queue management system 1440may detect that the current load of requests received at primary loadmanagement system 1455 is low, and that the generated resource-affinityparameter (e.g., generated after inputting one or more data points intoa supervised or semi-supervised machine-learning model) associated withthe corresponding user identifier (e.g., of the user operating mobiledevice 1420) is associated with a resource-affinity parameter thatindicates a likelihood that the user will ultimately transfer anyassigned access rights (e.g., a low likelihood that the user will meetan objective of ultimately accessing the resource). In someimplementations, first queue management system 1440 can generate thefirst throttle factor based on the current request load and theresource-affinity parameter. As a non-limiting example, the firstthrottle factor may be generated as a composite of the current requestload and the resource-affinity parameter (e.g., an average of the twovalues, if the current request load and the resource-affinity parameterare represented as values). It will be appreciated that variousalgorithms can be used to generate the first throttle factor using thecurrent request load and the resource-affinity parameter, such asweighted combinations, inverse relationships (e.g., when the currentrequest load is low, the first throttle factor can indicate a quickerspeed of providing the steps of the first workflow), dynamic algorithmsthat change based on contextual information, such as time of year, timeuntil the resource becomes available for accessing, and other suitablealgorithms.

Continuing with the non-limiting example above, if the current requestload is low (as compared to a threshold, such as fewer than 50 requestsan hour), then first queue management system 1440 can generate the firstthrottle factor to provide the steps of the first workflow quickly tomobile device 1420, even though the resource-affinity parameterindicates that the user associated with mobile device 1420 will notlikely meet the objective of ultimately accessing the resource. In thisnon-limiting example, if the current request load is low, then thethreshold of the resource-affinity parameter needed to control the speedof the steps of the first workflow relatively quickly is lower. Thisapproach enables the access rights to be assigned during time periods oflow request loads. However, as another non-limiting example, if thecurrent request load is high (as compared to a threshold, such as morethan 1000 requests an hour), then first queue management system 1440 cangenerate the first throttle factor to provide the steps of the firstworkflow to mobile device 1420 at a slow regular or irregular interval(or the mobile device 1420 can be blocked entirely from queryingdatabases for access rights). In this non-limiting example, because thecurrent request load is high, the threshold of the resource-affinityparameter needed to control the speed of the steps of the first workflowrelatively quickly is higher. Accordingly, because the non-limitingexample indicated that the resource-affinity parameter associated withmobile device 1420 indicates that the user operating mobile device 1420will not likely ultimately access the resource, first queue managementsystem 1440 provides the steps of the first workflow at a slow regularor irregular pace (or blocks the mobile device 1420 from querying thedatabases for assigning access rights).

It will be appreciated that first queue management system 1440 cangenerate an order parameter (e.g., a rank) for each user participatingin the first workflow during a given time period (e.g., a time periodprior to the resource being available for accessing with an accessright), in addition to or in lieu of generating the first throttlefactor. The order parameter can be used to position requests from userdevices into a queue. In some implementations, at a particular time,some or all queue positions within the queue can be processed accordingto the order parameter. For example, processing a queue position in thequeue can include performing a query of the database, such thatconstraints of the query are based on the constraints included in therequest that was stored in that particular queue position beingprocessed. For example, a constraint may include a number of accessrights, a location of access rights, a type of access right, and so on.In some implementations, the order parameter that is generated may becalculated so as to position requests in favorable queue positions forrequests associated with a resource-affinity parameter indicating alikelihood to meet an objective, and to position requests in lessfavorable queue positions for requests associated with aresource-affinity parameter indicating a likelihood of not meeting theobjective.

Continuing with the non-limiting example above, in some implementations,when the communication has been processed by the first queue managementsystem 1440, that means the first workflow has been completed.Completing the first indicates that mobile device 1420 has beenauthorized or otherwise enabled to query the databases that store theaccess rights. However, the first workflow enables users to query foraccess rights, however, the first workflow may not enable users torequest that one or more access rights resulting from the query beassigned to the user. The second workflow controlled by second queuemanagement system 1465 may provide the one or more steps involved incompleting the assignment of access rights to users. In someimplementations, the second workflow may include one or more steps thatresult in the assignment of access rights. These one or more steps mayinclude, but are not limited to, presenting an interface on mobiledevice 1420 or causing an interface to be presented on mobile device1420, receiving input from mobile device 1420 corresponding to therequisite information needed to complete the assignment process,receiving an instruction to complete the assignment of one or moreaccess rights to the requesting user or the requesting user's profile,and other suitable steps.

Second queue management system 1465 may generate a second throttlefactor, which can determine a speed or frequency (regular or irregular)at which the one or more steps of the second workflow are provided to orpresented on mobile device 1420. In some implementations, theresource-affinity parameter (e.g., the likelihood that the user willmeet an objective) and the current system load may be combined togenerate the second throttle factor. It will be appreciated that variousalgorithms can be used to generate the second throttle factor using thecurrent request load and the resource-affinity parameter, such asweighted combinations, inverse relationships (e.g., when the currentrequest load is low, the first throttle factor can indicate a quickerspeed of providing the steps of the first workflow), dynamic algorithmsthat change based on contextual information, such as time of year, timeuntil the resource becomes available for accessing, and other suitablealgorithms. In some implementations, request processor 1470 can completethe process of assigning an access right to mobile device 1420.Completing the process of assigning an access right may include storinga user identifier associated with mobile device 1420 in association withthe unique identifier representing the assigned access right. Requestprocessor 1470 may include one or more processors on which executablecode is stored, which, when executed, causes the user identifier to bestored in association with the access right in access right assignmentsdatabase 1475. Access right assignments database 1475 may include one ormore databases, which store some or all of the unique identifiers of theaccess rights, additional information associated with the access rights,such as time and location of the resource, and the assignmentinformation, such as the users to which an access right is assigned. Itwill be appreciated that access management system 1480 may beimplemented with first queue management system 1440 only, second queuemanagement system 1465 only, or any other number of queue managementsystems in addition to or in lieu of first queue management system 1440and second queue management system 1465. It will be appreciated that theresource-affinity parameter may refer to the contextualizedresource-affinity parameter. It will be appreciated that theresource-affinity parameter may refer to one of the global or localresource-affinity parameter.

FIG. 15 is a flow diagram illustrating an embodiment of process 1500 forcontinuously modifying queues in advance of access rights beingavailable for querying. Process 1500 can be performed, at least in part,by the primary load management system. Further, instead of requestingusers to provide login credentials to the access management system atthe end of the assignment process, the login prompt is moved earlier inthe assignment process. Process 1500 begins at block 1505 where a useroperates a computing device to transmit a signal representing a requestfor access rights for a particular resource (e.g., using an interfacethat enables querying of databases of access rights managed by theprimary load management system).

At block 1510, the primary load management system may receive the signalrepresenting the user's request for access rights to a request. Inresponse, the primary load management system may route the user to aninterface associated with the primary load management system. Forexample, the primary load management system may transmit interface dataof the interface to the computing device operated by the user. Theinterface may be accessed using a browser (e.g., a mobile web browser)or by a native application running on a mobile device. At block 1515,the primary load management system can be configured to receive thelogin credential inputted by the user and verify whether the logincredentials are stored in internal security databases. If the user'slogin credentials are verified, the primary load management system canaccess the user's resource-affinity parameter at block 1520. In someimplementations, the user's resource-affinity parameter can be used todetermine whether or not to initiate an additional process flowassociated with the resource. The primary load management system canidentify a queue position to be assigned to the user's request, suchthat the queue position is a position in an existing queue that isdetermined based on the accessed resource-affinity parameter. Theexisting queue may include a plurality of queue positions. Each queueposition can correspond to a particular user's access right request.Users with resource-affinity parameters that indicate a higherlikelihood of meeting an objective may be placed in favorable queuepositions in the existing queue. For example, a favorable queue positionmay be a position in the queue that will be processed earlier thanothers. The user's resource-affinity parameter may determine which queueposition to place the user's request for access rights.

At block 1525, the primary load management system may modify theexisting queue to include the queue position that corresponds to theuser (identified at block 1520). At block 1530, the primary loadmanagement system may continuously modify the existing queue as newusers access the primary load management system and request accessrights to the resource. Each resource may be associated with one or morequeues. Each queue may store one or more queue positions. Each queueposition may store a user request for assignment of one or more accessrights to that resource. For example, new queue positions can beinserted into the queue and the placement of the new queue positions inthe queue is determined based on the user's resource-affinity parameter.It will be appreciated that the user's resource-affinity parameter canbe accessed for queuing purposes in other situations, as well. However,the location of the placement in the queue can be modified depending onthe user's resource-affinity parameter. For example, if the user has aresource-affinity parameter that indicates a high likelihood of meetingan objective, the user may be placed at the beginning of the queue. Itwill also be appreciated that the queue placement can be based onfactors other than, or in addition to, the resource-affinity parameter.Non-limiting examples of other factors include the value associated withthe access rights or the number of access rights requested forassignment, the likelihood that the user will meet an objectiveassociated with the specific resource, and other suitable factors.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments can be practiced without these specific details.For example, circuits can be shown in block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquescan be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove can be done in various ways. For example, these techniques,blocks, steps and means can be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitscan be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments can be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart can describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations can be re-arranged. A process is terminated when itsoperations are completed, but could have additional steps not includedin the figure. A process can correspond to a method, a function, aprocedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination corresponds to a return of the functionto the calling function or the main function.

Furthermore, embodiments can be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks can bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction can represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment can becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. can be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies can beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions can be used in implementing themethodologies described herein. For example, software codes can bestored in a memory. Memory can be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium”, “storage” or“memory” can represent one or more memories for storing data, includingread only memory (ROM), random access memory (RAM), magnetic RAM, corememory, magnetic disk storage mediums, optical storage mediums, flashmemory devices and/or other machine readable mediums for storinginformation. The term “machine-readable medium” includes, but is notlimited to portable or fixed storage devices, optical storage devices,wireless channels, and/or various other storage mediums capable ofstoring that contain or carry instruction(s) and/or data.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed is:
 1. A computer-implemented method comprising:receiving, at a primary load management system, a communication from auser device, the communication corresponding to a request for one ormore access rights to a resource, and the primary load management systemmanaging assignment of access rights to resources; determining a useridentifier associated with the user device, the determination of theuser identifier being based on the communication; accessing a first setof data points associated with the user identifier; generating a localresource-affinity parameter, the local resource-affinity parameterrepresenting a likelihood that a user associated with the user devicewill access the resource; accessing a second set of data pointsassociated with the user identifier, at least one data point of thesecond set of data points being different from the first set of datapoints; generating a global resource-affinity parameter, the globalresource-affinity parameter representing a likelihood that the userassociated with the user device will access any resource; determiningwhether or not to assign the one or more access rights to the resourceto the user device, the determination being based on a combination ofthe local resource-affinity parameter and the global resource-affinityparameter; and in response to determining to assign the one or moreaccess rights to the resource, assigning the one or more access rightsto the user device, the assignment of the one or more access rights tothe user device enabling the user device to access the resource during adefined time period.
 2. The computer-implemented method of claim 1,further comprising: in response to determining to block the assignmentof the one or more access rights to the user device, inhibiting theassignment of the one or more access rights to the user device, and theinhibiting of the assignment of the one or more access rights inhibitingthe user device and the user associated with the user device fromaccessing the resource.
 3. The computer-implemented method of claim 1,wherein the global resource-affinity parameter represents a degree towhich the user device is predicted to be operated by a bot-script. 4.The computer-implemented method of claim 1, further comprising: feedingeach of the local resource-affinity parameter and the globalresource-affinity parameter into a machine-learning model to generate aresult, the result being used as a basis for determining whether or notto assign the one or more access rights to the user device.
 5. Thecomputer-implemented method of claim 1, wherein the first set of datapoints is fed into a trained machine-learning model to generate aresult, the result predicting whether or not the user associated withthe user device will access the resource using the one or more accessrights.
 6. The computer-implemented method of claim 1, wherein thesecond set of data points is fed into a trained machine-learning modelto generate a result, the result predicting whether or not the userdevice is operated by a bot-script.
 7. The computer-implemented methodof claim 1, wherein the first set of data points includes a first datapoint indicating whether or not the user device has previously beenassigned an access right to the resource, and wherein the second set ofdata points includes a second data point indicating whether or not theuser device has previously been assigned any access right to anyresource.
 8. A system, comprising: one or more data processors; and anon-transitory computer-readable storage medium containing instructionswhich, when executed on the one or more data processors, cause the oneor more data processors to perform operations including: receiving, at aprimary load management system, a communication from a user device, thecommunication corresponding to a request for one or more access rightsto a resource, and the primary load management system managingassignment of access rights to resources; determining a user identifierassociated with the user device, the determination of the useridentifier being based on the communication; accessing a first set ofdata points associated with the user identifier; generating a localresource-affinity parameter, the local resource-affinity parameterrepresenting a likelihood that a user associated with the user devicewill access the resource; accessing a second set of data pointsassociated with the user identifier, at least one data point of thesecond set of data points being different from the first set of datapoints; generating a global resource-affinity parameter, the globalresource-affinity parameter representing a likelihood that the userassociated with the user device will access any resource; determiningwhether or not to assign the one or more access rights to the resourceto the user device, the determination being based on a combination ofthe local resource-affinity parameter and the global resource-affinityparameter; and in response to determining to assign the one or moreaccess rights to the resource, assigning the one or more access rightsto the user device, the assignment of the one or more access rights tothe user device enabling the user device to access the resource during adefined time period.
 9. The system of claim 8, further comprising: inresponse to determining to block the assignment of the one or moreaccess rights to the user device, inhibiting the assignment of the oneor more access rights to the user device, and the inhibiting of theassignment of the one or more access rights inhibiting the user deviceand the user associated with the user device from accessing theresource.
 10. The system of claim 8, wherein the globalresource-affinity parameter represents a degree to which the user deviceis predicted to be operated by a bot-script.
 11. The system of claim 8,further comprising: feeding each of the local resource-affinityparameter and the global resource-affinity parameter into amachine-learning model to generate a result, the result being used as abasis for determining whether or not to assign the one or more accessrights to the user device.
 12. The system of claim 8, wherein the firstset of data points is fed into a trained machine-learning model togenerate a result, the result predicting whether or not the userassociated with the user device will access the resource using the oneor more access rights.
 13. The system of claim 8, wherein the second setof data points is fed into a trained machine-learning model to generatea result, the result predicting whether or not the user device isoperated by a bot-script.
 14. The system of claim 8, wherein the firstset of data points includes a first data point indicating whether or notthe user device has previously been assigned an access right to theresource, and wherein the second set of data points includes a seconddata point indicating whether or not the user device has previously beenassigned any access right to any resource.
 15. A computer-programproduct tangibly embodied in a non-transitory machine-readable storagemedium, including instructions configured to cause a data processingapparatus to perform operations including: receiving, at a primary loadmanagement system, a communication from a user device, the communicationcorresponding to a request for one or more access rights to a resource,and the primary load management system managing assignment of accessrights to resources; determining a user identifier associated with theuser device, the determination of the user identifier being based on thecommunication; accessing a first set of data points associated with theuser identifier; generating a local resource-affinity parameter, thelocal resource-affinity parameter representing a likelihood that a userassociated with the user device will access the resource; accessing asecond set of data points associated with the user identifier, at leastone data point of the second set of data points being different from thefirst set of data points; generating a global resource-affinityparameter, the global resource-affinity parameter representing alikelihood that the user associated with the user device will access anyresource; determining whether or not to assign the one or more accessrights to the resource to the user device, the determination being basedon a combination of the local resource-affinity parameter and the globalresource-affinity parameter; and in response to determining to assignthe one or more access rights to the resource, assigning the one or moreaccess rights to the user device, the assignment of the one or moreaccess rights to the user device enabling the user device to access theresource during a defined time period.
 16. The computer-program productof claim 15, further comprising: in response to determining to block theassignment of the one or more access rights to the user device,inhibiting the assignment of the one or more access rights to the userdevice, and the inhibiting of the assignment of the one or more accessrights inhibiting the user device and the user associated with the userdevice from accessing the resource.
 17. The computer-program product ofclaim 15, wherein the global resource-affinity parameter represents adegree to which the user device is predicted to be operated by abot-script.
 18. The computer-program product of claim 15, furthercomprising: feeding each of the local resource-affinity parameter andthe global resource-affinity parameter into a machine-learning model togenerate a result, the result being used as a basis for determiningwhether or not to assign the one or more access rights to the userdevice.
 19. The computer-program product of claim 15, wherein the firstset of data points is fed into a trained machine-learning model togenerate a result, the result predicting whether or not the userassociated with the user device will access the resource using the oneor more access rights.
 20. The computer-program product of claim 15,wherein the second set of data points is fed into a trainedmachine-learning model to generate a result, the result predictingwhether or not the user device is operated by a bot-script.